mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-30 19:51:31 -04:00
block: fix mismerge of the DISK_EVENT_MEDIA_CHANGE removal
Jens' back-merge commit698567f3fa("Merge commit 'v2.6.39' into for-2.6.40/core") was incorrectly done, and re-introduced the DISK_EVENT_MEDIA_CHANGE lines that had been removed earlier in commits -9fd097b149("block: unexport DISK_EVENT_MEDIA_CHANGE for legacy/fringe drivers") -7eec77a181("ide: unexport DISK_EVENT_MEDIA_CHANGE for ide-gd and ide-cd") because of conflicts with the "g->flags" updates near-by by commitd4dc210f69("block: don't block events on excl write for non-optical devices") As a result, we re-introduced the hanging behavior due to infinite disk media change reports. Tssk, tssk, people! Don't do back-merges at all, and *definitely* don't do them to hide merge conflicts from me - especially as I'm likely better at merging them than you are, since I do so many merges. Reported-by: Steven Rostedt <[email protected]> Cc: Jens Axboe <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
This commit is contained in:
parent
3f303103b8
commit
0f48f26009
3 changed files with 0 additions and 3 deletions
|
|
@ -627,7 +627,6 @@ static int viocd_probe(struct vio_dev *vdev, const struct vio_device_id *id)
|
|||
gendisk->fops = &viocd_fops;
|
||||
gendisk->flags = GENHD_FL_CD | GENHD_FL_REMOVABLE |
|
||||
GENHD_FL_BLOCK_EVENTS_ON_EXCL_WRITE;
|
||||
gendisk->events = DISK_EVENT_MEDIA_CHANGE;
|
||||
set_capacity(gendisk, 0);
|
||||
gendisk->private_data = d;
|
||||
d->viocd_disk = gendisk;
|
||||
|
|
|
|||
Loading…
Reference in a new issue