* [PATCH 05/09] [SCSI] mpt2sas : Fix for max_sectors warning message is stating the incorrect range
@ 2012-07-17 10:26 sreekanth.reddy
0 siblings, 0 replies; only message in thread
From: sreekanth.reddy @ 2012-07-17 10:26 UTC (permalink / raw)
To: linux-scsi, Sathya.Prakash, Nagalakshmi.Nandigama,
sreekanth.reddy; +Cc: jejb
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>
---
diff --git a/drivers/scsi/mpt2sas/mpt2sas_scsih.c b/drivers/scsi/mpt2sas/mpt2sas_scsih.c
index 0f4f971..4a09ace 100644
--- a/drivers/scsi/mpt2sas/mpt2sas_scsih.c
+++ b/drivers/scsi/mpt2sas/mpt2sas_scsih.c
@@ -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;
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2012-07-17 10:25 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-07-17 10:26 [PATCH 05/09] [SCSI] mpt2sas : Fix for max_sectors warning message is stating the incorrect range sreekanth.reddy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox