summaryrefslogtreecommitdiffstats
path: root/block/blk-merge.c
diff options
context:
space:
mode:
authorNick Andrew <nick@nick-andrew.net>2008-04-21 09:51:04 +0200
committerJens Axboe <jens.axboe@oracle.com>2008-04-21 09:51:04 +0200
commitee86418d39f28dd10d27c9d7906d8c26c1293e69 (patch)
treee9314f3ad14b350fabdccc9905096e6e22c2d55b /block/blk-merge.c
parent6195057f5809e93cdb1ec733f7b9c87fe2212f98 (diff)
downloadtalos-obmc-linux-ee86418d39f28dd10d27c9d7906d8c26c1293e69.tar.gz
talos-obmc-linux-ee86418d39f28dd10d27c9d7906d8c26c1293e69.zip
Kconfig: clean up block/Kconfig help descriptions
Modify the help descriptions of block/Kconfig for clarity, accuracy and consistency. Refactor the BLOCK description a bit. The wording "This permits ... to be removed" isn't quite right; the block layer is removed when the option is disabled, whereas most descriptions talk about what happens when the option is enabled. Reformat the list of what is affected by disabling the block layer. Add more examples of large block devices to LBD and strive for technical accuracy; block devices of size _exactly_ 2TB require CONFIG_LBD, not only "bigger than 2TB". Also try to say (perhaps not very clearly) that the config option is only needed when you want to have individual block devices of size >= 2TB, for example if you had 3 x 1TB disks in your computer you'd have a total storage size of 3TB but you wouldn't need the option unless you want to aggregate those disks into a RAID or LVM. Improve terminology and grammar on BLK_DEV_IO_TRACE. I also added the boilerplate "If unsure, say N" to most options. Precisely say "2TB and larger" for LSF. Indent the help text for BLK_DEV_BSG by 2 spaces in accordance with the standard. Signed-off-by: Nick Andrew <nick@nick-andrew.net> Cc: "Randy.Dunlap" <rdunlap@xenotime.net> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
Diffstat (limited to 'block/blk-merge.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud