[SCSI] mpt2sas: Fix for max_sectors warning message is stating the incorrect range
authorsreekanth.reddy@lsi.com <sreekanth.reddy@lsi.com>
Tue, 17 Jul 2012 10:26:09 +0000 (15:56 +0530)
committerJames Bottomley <JBottomley@Parallels.com>
Fri, 24 Aug 2012 09:10:26 +0000 (13:10 +0400)
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: Sreekanth Reddy <sreekanth.reddy@lsi.com>
Signed-off-by: James Bottomley <JBottomley@Parallels.com>
drivers/scsi/mpt2sas/mpt2sas_scsih.c

index fc18591cd9322fc8769b4b2b3190c20b89812b0e..ab3d9d3e805f0b2b3cf9728860b85e1699b0e963 100644 (file)
@@ -8055,8 +8055,8 @@ _scsih_probe(struct pci_dev *pdev, const struct pci_device_id *id)
        if (max_sectors != 0xFFFF) {
                if (max_sectors < 64) {
                        shost->max_sectors = 64;
-                       printk(MPT2SAS_WARN_FMT "Invalid value %d passed "
-                           "for max_sectors, range is 64 to 8192. Assigning "
+                       printk(MPT2SAS_WARN_FMT "Invalid value %d passed "\
+                           "for max_sectors, range is 64 to 32767. Assigning "\
                            "value of 64.\n", ioc->name, max_sectors);
                } else if (max_sectors > 32767) {
                        shost->max_sectors = 32767;