diff options
author | Martin K. Petersen <martin.petersen@oracle.com> | 2010-02-26 00:20:38 -0500 |
---|---|---|
committer | Jens Axboe <jens.axboe@oracle.com> | 2010-02-26 07:58:08 -0500 |
commit | 086fa5ff0854c676ec333760f4c0154b3b242616 (patch) | |
tree | ee63fb3c7c7d964bd799355b7cde18ba95f91f07 /drivers/scsi/scsi_lib.c | |
parent | eb28d31bc97e6374d81f404da309401ffaed467b (diff) |
block: Rename blk_queue_max_sectors to blk_queue_max_hw_sectors
The block layer calling convention is blk_queue_<limit name>.
blk_queue_max_sectors predates this practice, leading to some confusion.
Rename the function to appropriately reflect that its intended use is to
set max_hw_sectors.
Also introduce a temporary wrapper for backwards compability. This can
be removed after the merge window is closed.
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
Diffstat (limited to 'drivers/scsi/scsi_lib.c')
-rw-r--r-- | drivers/scsi/scsi_lib.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c index c6642423cc67..ac3cca74bdfb 100644 --- a/drivers/scsi/scsi_lib.c +++ b/drivers/scsi/scsi_lib.c | |||
@@ -1627,7 +1627,7 @@ struct request_queue *__scsi_alloc_queue(struct Scsi_Host *shost, | |||
1627 | blk_queue_max_hw_segments(q, shost->sg_tablesize); | 1627 | blk_queue_max_hw_segments(q, shost->sg_tablesize); |
1628 | blk_queue_max_phys_segments(q, SCSI_MAX_SG_CHAIN_SEGMENTS); | 1628 | blk_queue_max_phys_segments(q, SCSI_MAX_SG_CHAIN_SEGMENTS); |
1629 | 1629 | ||
1630 | blk_queue_max_sectors(q, shost->max_sectors); | 1630 | blk_queue_max_hw_sectors(q, shost->max_sectors); |
1631 | blk_queue_bounce_limit(q, scsi_calculate_bounce_limit(shost)); | 1631 | blk_queue_bounce_limit(q, scsi_calculate_bounce_limit(shost)); |
1632 | blk_queue_segment_boundary(q, shost->dma_boundary); | 1632 | blk_queue_segment_boundary(q, shost->dma_boundary); |
1633 | dma_set_seg_boundary(dev, shost->dma_boundary); | 1633 | dma_set_seg_boundary(dev, shost->dma_boundary); |