From: 'Tejun Heo' <tj@kernel.org>
To: Jingoo Han <jg1.han@samsung.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH V2 2/2] ahci_platform: use dev_info() instead of printk()
Date: Mon, 7 Oct 2013 15:25:02 -0400 [thread overview]
Message-ID: <20131007192502.GH27396@htj.dyndns.org> (raw)
In-Reply-To: <20131007191310.GF27396@htj.dyndns.org>
On Mon, Oct 07, 2013 at 03:13:10PM -0400, 'Tejun Heo' wrote:
> On Sat, Oct 05, 2013 at 09:15:59AM +0900, Jingoo Han wrote:
> > Change "raw" printk() call to dev_info() to provide a better
> > message to userspace so it can properly identify the device
> > and not just have to guess.
> >
> > Signed-off-by: Jingoo Han <jg1.han@samsung.com>
>
> Applied to libata/for-3.13.
Strike that. Applied to libata/for-3.12-fixes.
Thanks.
--
tejun
prev parent reply other threads:[~2013-10-07 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 0:15 [PATCH V2 1/2] ahci: use dev_info() instead of printk() Jingoo Han
2013-10-05 0:15 ` [PATCH V2 2/2] ahci_platform: " Jingoo Han
2013-10-07 19:13 ` 'Tejun Heo'
2013-10-07 19:25 ` 'Tejun Heo' [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=20131007192502.GH27396@htj.dyndns.org \
--to=tj@kernel.org \
--cc=jg1.han@samsung.com \
--cc=linux-ide@vger.kernel.org \
/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).