Skip to contentSkip to conversation

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

PATCH New [email protected] 1 participant 1 message Jul 17, 2012 SCSI

lore
Share & tools
lore
#0 lore raw

PATCH 5/9 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.

---

drivers/scsi/mpt2sas/mpt2sas_scsih.c +2 -2
index 0f4f971..4a09ace 100644
@@ -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;