Commit eece5de5 authored by sreekanth.reddy@lsi.com's avatar sreekanth.reddy@lsi.com Committed by James Bottomley

[SCSI] mpt2sas: Fix for max_sectors warning message is stating the incorrect range

When specifying the command line option "max_sectors" less than 64, then
warning message should provide correct upper boundary value 32767 instead of
8192.
Signed-off-by: default avatarSreekanth Reddy <sreekanth.reddy@lsi.com>
Signed-off-by: default avatarJames Bottomley <JBottomley@Parallels.com>
parent 6c265660
...@@ -8055,8 +8055,8 @@ _scsih_probe(struct pci_dev *pdev, const struct pci_device_id *id) ...@@ -8055,8 +8055,8 @@ _scsih_probe(struct pci_dev *pdev, const struct pci_device_id *id)
if (max_sectors != 0xFFFF) { if (max_sectors != 0xFFFF) {
if (max_sectors < 64) { if (max_sectors < 64) {
shost->max_sectors = 64; shost->max_sectors = 64;
printk(MPT2SAS_WARN_FMT "Invalid value %d passed " printk(MPT2SAS_WARN_FMT "Invalid value %d passed "\
"for max_sectors, range is 64 to 8192. Assigning " "for max_sectors, range is 64 to 32767. Assigning "\
"value of 64.\n", ioc->name, max_sectors); "value of 64.\n", ioc->name, max_sectors);
} else if (max_sectors > 32767) { } else if (max_sectors > 32767) {
shost->max_sectors = 32767; shost->max_sectors = 32767;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment