summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorJan Höppner <hoeppner@linux.vnet.ibm.com>2016-06-30 13:58:51 +0300
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2016-10-28 11:09:01 +0300
commit5303e6578f4a57e3be13a60825d3ae9f0d18af36 (patch)
tree6d2cc1ae0ff82257ef6c8e0188d92445b4aae056 /drivers
parent237d6e6884136923b6bd26d5141ebe1d065960c9 (diff)
downloadlinux-5303e6578f4a57e3be13a60825d3ae9f0d18af36.tar.xz
s390/dasd: Make setting queue_max_segments more explicit
Currently the block queue value max_segments is set to -1L, which is then implicitly casted to unsigned short in blk_queue_max_segments. This results in 65535 (64k) max_segments. Even though the resulting value is correct, setting it implicitly using -1L is rather confusing. Set the value explicitly using the USHRT_MAX macro instead. Reviewed-by: Stefan Haberland <sth@linux.vnet.ibm.com> Signed-off-by: Jan Höppner <hoeppner@linux.vnet.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/s390/block/dasd.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/s390/block/dasd.c b/drivers/s390/block/dasd.c
index 1de089019268..6a0c9df8f323 100644
--- a/drivers/s390/block/dasd.c
+++ b/drivers/s390/block/dasd.c
@@ -3140,7 +3140,7 @@ static void dasd_setup_queue(struct dasd_block *block)
blk_queue_logical_block_size(block->request_queue,
block->bp_block);
blk_queue_max_hw_sectors(block->request_queue, max);
- blk_queue_max_segments(block->request_queue, -1L);
+ blk_queue_max_segments(block->request_queue, USHRT_MAX);
/* with page sized segments we can translate each segement into
* one idaw/tidaw
*/