diff options
| author | NeilBrown | 2014-12-15 02:56:56 +0100 |
|---|---|---|
| committer | NeilBrown | 2015-02-03 22:35:52 +0100 |
| commit | 85572d7c75fd5b9fa3fc911e1c99c68ec74903a0 (patch) | |
| tree | c5cddb46ed2460752c371c2775521de87d1450e2 /drivers/md/raid5.c | |
| parent | md/raid5: need_this_block: tidy/fix last condition. (diff) | |
| download | kernel-qcow2-linux-85572d7c75fd5b9fa3fc911e1c99c68ec74903a0.tar.gz kernel-qcow2-linux-85572d7c75fd5b9fa3fc911e1c99c68ec74903a0.tar.xz kernel-qcow2-linux-85572d7c75fd5b9fa3fc911e1c99c68ec74903a0.zip | |
md: rename mddev->write_lock to mddev->lock
This lock is used for (slightly) more than helping with writing
superblocks, and it will soon be extended further. So the
name is inappropriate.
Also, the _irq variant hasn't been needed since 2.6.37 as it is
never taking from interrupt or bh context.
So:
-rename write_lock to lock
-document what it protects
-remove _irq ... except in md_flush_request() as there
is no wait_event_lock() (with no _irq). This can be
cleaned up after appropriate changes to wait.h.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/raid5.c')
0 files changed, 0 insertions, 0 deletions