From: Chris Ball <cjb@laptop.org>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: linux-mmc@vger.kernel.org, Lior Amsalem <alior@marvell.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
Gregory Clement <gregory.clement@free-electrons.com>,
Maen Suleiman <maen@marvell.com>, Ralph Droms <rdroms@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH for 3.10 v2] mmc: mvsdio: use dev_*() API instead of pr_*() API
Date: Fri, 22 Mar 2013 13:18:13 -0400 [thread overview]
Message-ID: <87zjxvjqui.fsf@octavius.laptop.org> (raw)
In-Reply-To: <1363959441-30744-1-git-send-email-thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Fri, 22 Mar 2013 14:37:21 +0100")
Hi,
On Fri, Mar 22 2013, Thomas Petazzoni wrote:
> The mvsdio driver was already using some dev_*() functions to print
> some messages, but still using pr_*() functions for some others. This
> patch converts all messages to use dev_*() functions.
>
> Many of the pr_*() function calls were printing the output of
> mmc_hostname() to preprend the message with an identifier for the
> device. Since the dev_*() functions do that automatically, this patch
> also gets rid of those string prefixes.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> This is for 3.10.
>
> Changes between v1 and v2:
>
> * Fix incorrect format string. A "%s" was left, even though the
> mmc_hostname() argument was removed due to the conversion to the
> dev_*() API.
Thanks, I've updated to v2 in mmc-next for 3.10.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2013-03-22 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 13:37 [PATCH for 3.10 v2] mmc: mvsdio: use dev_*() API instead of pr_*() API Thomas Petazzoni
2013-03-22 17:18 ` Chris Ball [this message]
2013-03-22 20:44 ` Ralph Droms
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=87zjxvjqui.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=maen@marvell.com \
--cc=rdroms@gmail.com \
--cc=thomas.petazzoni@free-electrons.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