From: Bjorn Helgaas <bhelgaas@google.com>
To: Sumit Saxena <sumit.saxena@avagotech.com>
Cc: Kashyap Desai <kashyap.desai@avagotech.com>,
Uday Lingala <uday.lingala@avagotech.com>,
"PDL,MEGARAIDLINUX" <megaraidlinux.pdl@avagotech.com>,
"James E.J. Bottomley" <JBottomley@odin.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 3/3] megaraid_sas: use dev_printk when possible
Date: Tue, 5 May 2015 13:30:19 -0500 [thread overview]
Message-ID: <CAErSpo5bmtbq_ji8OM4_fbz4ix1xLw2LUD6tbdr0jKNSzN5xyw@mail.gmail.com> (raw)
In-Reply-To: <3a237529c12b20e6b7a4c8de82b6a3ee@mail.gmail.com>
On Wed, Apr 29, 2015 at 12:44 AM, Sumit Saxena
<sumit.saxena@avagotech.com> wrote:
>>-----Original Message-----
>>From: Bjorn Helgaas [mailto:bhelgaas@google.com]
>>Sent: Wednesday, April 29, 2015 4:44 AM
>>To: Kashyap Desai; Uday Lingala; Sumit Saxena
>>Cc: megaraidlinux.pdl@avagotech.com; James E.J. Bottomley; linux-
>>kernel@vger.kernel.org; linux-scsi@vger.kernel.org
>>Subject: [PATCH 3/3] megaraid_sas: use dev_printk when possible
>>
>>Use dev_printk() when possible to make messages more useful.
>> ...
> Currently few patches are sent for megaraid_sas driver and after applying
> those patches, this patch may not apply cleanly. Once those patches are
> accepted, I will rebase and send this patch again.
OK, sure. Do you want me to repost these after your patches get
merged somewhere?
Bjorn
prev parent reply other threads:[~2015-05-05 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 23:13 [PATCH 0/3] megaraid: use dev_printk() when possible Bjorn Helgaas
2015-04-28 23:14 ` [PATCH 1/3] megaraid: use dev_printk " Bjorn Helgaas
2015-04-29 5:32 ` Sumit Saxena
2015-04-28 23:14 ` [PATCH 2/3] megaraid_sas: " Bjorn Helgaas
2015-04-29 5:39 ` Sumit Saxena
2015-06-01 1:03 ` James Bottomley
2015-04-28 23:14 ` [PATCH 3/3] " Bjorn Helgaas
2015-04-29 5:44 ` Sumit Saxena
2015-05-05 18:30 ` Bjorn Helgaas [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=CAErSpo5bmtbq_ji8OM4_fbz4ix1xLw2LUD6tbdr0jKNSzN5xyw@mail.gmail.com \
--to=bhelgaas@google.com \
--cc=JBottomley@odin.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).