From: Hannes Reinecke <hare@suse.de>
To: Bjorn Helgaas <bhelgaas@google.com>,
Kashyap Desai <kashyap.desai@avagotech.com>,
Uday Lingala <uday.lingala@avagotech.com>,
Sumit Saxena <sumit.saxena@avagotech.com>
Cc: megaraidlinux.pdl@avagotech.com, linux-scsi@vger.kernel.org,
"James E.J. Bottomley" <JBottomley@odin.com>,
linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v3 1/3] megaraid : use dev_printk when possible
Date: Wed, 08 Jul 2015 12:44:30 +0200 [thread overview]
Message-ID: <559CFF0E.30803@suse.de> (raw)
In-Reply-To: <20150707205225.6218.32600.stgit@bhelgaas-glaptop2.roam.corp.google.com>
On 07/07/2015 10:52 PM, Bjorn Helgaas wrote:
> Use dev_printk() when possible to make messages more useful.
>
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> ---
> drivers/scsi/megaraid.c | 140 ++++++++++++++++++++++-------------------------
> 1 file changed, 66 insertions(+), 74 deletions(-)
>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-07-08 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 20:52 [PATCH v3 0/3] megaraid: use dev_printk() when possible Bjorn Helgaas
2015-07-07 20:52 ` [PATCH v3 1/3] megaraid : use dev_printk " Bjorn Helgaas
2015-07-08 6:08 ` Sumit Saxena
2015-07-08 10:44 ` Hannes Reinecke [this message]
2015-07-07 20:52 ` [PATCH v3 2/3] megaraid_sas " Bjorn Helgaas
2015-07-08 9:13 ` Sumit Saxena
2015-07-08 10:47 ` Hannes Reinecke
2015-07-08 13:28 ` Bjorn Helgaas
2015-07-07 20:52 ` [PATCH v3 3/3] megaraid_sas : fix whitespace errors Bjorn Helgaas
2015-07-08 9:13 ` Sumit Saxena
2015-07-08 10:48 ` Hannes Reinecke
2015-08-26 14:36 ` James Bottomley
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=559CFF0E.30803@suse.de \
--to=hare@suse.de \
--cc=JBottomley@odin.com \
--cc=bhelgaas@google.com \
--cc=hch@lst.de \
--cc=joe@perches.com \
--cc=kashyap.desai@avagotech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=megaraidlinux.pdl@avagotech.com \
--cc=sumit.saxena@avagotech.com \
--cc=uday.lingala@avagotech.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;
as well as URLs for NNTP newsgroup(s).