summaryrefslogtreecommitdiffstats
path: root/drivers/md
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2011-04-20 15:38:07 +1000
committerNeilBrown <neilb@suse.de>2011-04-20 15:38:07 +1000
commit2b7da309ffe602d222558cee4d7e407b96e34b3a (patch)
tree34e3dc62926676983855aa0a4aa100aaabc98169 /drivers/md
parentf0e615c3cb72b42191b558c130409335812621d8 (diff)
downloadlinux-2b7da309ffe602d222558cee4d7e407b96e34b3a.tar.bz2
md/raid5: remove setting of ->queue_lock
We previously needed to set ->queue_lock to match the raid5 device_lock so we could safely use queue_flag_* operations (e.g. for plugging). which test the ->queue_lock is in fact locked. However that need has completely gone away and is unlikely to come back to remove this now-pointless setting. Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md')
-rw-r--r--drivers/md/raid5.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index f301e6ae220c..179bdfc4d03a 100644
--- a/drivers/md/raid5.c
+++ b/drivers/md/raid5.c
@@ -5151,7 +5151,6 @@ static int run(mddev_t *mddev)
mddev->queue->backing_dev_info.congested_data = mddev;
mddev->queue->backing_dev_info.congested_fn = raid5_congested;
- mddev->queue->queue_lock = &conf->device_lock;
chunk_size = mddev->chunk_sectors << 9;
blk_queue_io_min(mddev->queue, chunk_size);