From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Saxena, Sumit" <Sumit.Saxena@lsi.com>
Cc: Jasper Spaans <spaans@fox-it.com>,
DL-MegaRAID Linux <megaraidlinux@lsi.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] megaraid_sas: make the log message about rescanning more informative.
Date: Thu, 13 Mar 2014 14:37:43 +0400 [thread overview]
Message-ID: <1394707063.2192.17.camel@dabdike> (raw)
In-Reply-To: <ed904388f93d4981a2bdefc6a622acdd@DM2PR07MB400.namprd07.prod.outlook.com>
On Wed, 2014-01-08 at 12:28 +0000, Saxena, Sumit wrote:
>
> >-----Original Message-----
> >From: Jasper Spaans [mailto:spaans@fox-it.com]
> >Sent: Friday, October 25, 2013 5:53 PM
> >To: DL-MegaRAID Linux
> >Cc: linux-scsi@vger.kernel.org
> >Subject: [PATCH] megaraid_sas: make the log message about rescanning
> >more informative.
> >
> >Hi,
> >
> >I was working on one of our servers, and saw the following interesting
> >message in dmesg:
> >
> >[20961024.720972] scanning ...
> >
> >This scared me somewhat. Please find a patch to make it easier to see where
> >this message is coming from.
> >
> >Cheers,
> >Jasper
> >
> >---
> > drivers/scsi/megaraid/megaraid_sas_base.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/drivers/scsi/megaraid/megaraid_sas_base.c
> >b/drivers/scsi/megaraid/megaraid_sas_base.c
> >index 1f0ca68..3457289 100644
> >--- a/drivers/scsi/megaraid/megaraid_sas_base.c
> >+++ b/drivers/scsi/megaraid/megaraid_sas_base.c
> >@@ -5461,7 +5461,7 @@ megasas_aen_polling(struct work_struct *work)
> > }
> >
> > if (doscan) {
> >- printk(KERN_INFO "scanning ...\n");
> >+ printk(KERN_INFO "Rescanning MegaRAID devices ...\n");
> > megasas_get_pd_list(instance);
> > for (i = 0; i < MEGASAS_MAX_PD_CHANNELS; i++) {
> > for (j = 0; j < MEGASAS_MAX_DEV_PER_CHANNEL;
> >j++) {
> >--
> >1.7.9.5
> Acked-by: Sumit Saxena <sumit.saxena@lsi.com>
I'd prefer consistency for this: Most of the messages in this driver
have a megasas: prefix ... but there are quite a large number that don't
(and which probably should have). If this is necessary, please use the
standard driver prefix.
Thanks,
James
prev parent reply other threads:[~2014-03-13 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 12:23 [PATCH] megaraid_sas: make the log message about rescanning more informative Jasper Spaans
2014-01-08 12:28 ` Saxena, Sumit
2014-03-13 10:37 ` James Bottomley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1394707063.2192.17.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=Sumit.Saxena@lsi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=megaraidlinux@lsi.com \
--cc=spaans@fox-it.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox