From: David Brown <davidb@codeaurora.org>
To: Joe Perches <joe@perches.com>
Cc: Pavel Pisa <ppisa@pikron.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Daniel Walker <dwalker@fifo99.com>,
Harald Welte <HaraldWelte@viatech.com>,
Pierre Ossman <pierre@ossman.eu>, Chris Ball <cjb@laptop.org>,
Alex Dubov <oakad@yahoo.com>,
linux-arm-msm@vger.kernel.org,
Bruce Chang <brucechang@via.com.tw>,
Ian Molton <ian@mnementh.co.uk>, Ben Dooks <ben-linux@fluff.org>,
Tony Olech <tony.olech@elandigitalsystems.com>,
linux-omap@vger.kernel.org, David Brown <davidb@codeaurora.org>,
linux-arm-kernel@lists.infradead.org,
Nicolas Pitre <nico@fluxnic.net>,
linux-usb@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bryan Huntsman <bryanh@codeaurora.org>,
Manuel Lauss <manuel.lauss@gmail.com>,
Jarkko Lavinen <jarkko.lavinen@nokia.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: [PATCH] mmc: Use pr_<level>, add and use mmc_<level>
Date: Thu, 11 Aug 2011 13:34:16 -0700 [thread overview]
Message-ID: <20110811203416.GA12740@huya.qualcomm.com> (raw)
In-Reply-To: <1441985db03ab10b067332f7d4b75b607921441b.1313094012.git.joe@perches.com>
On Thu, Aug 11, 2011 at 01:21:24PM -0700, Joe Perches wrote:
> Use current logging styles.
>
> Add an mmc_printk function to reduce overall size
> by centralizing the mmc_hostname use.
>
> Because pr_fmt(fmt) KBUILD_MODNAME is used,
> some logging prefixes are changed.
> For instance from "SDIO:" to "mmc_core:"
>
> Add macros for mmc_err, mmc_warn, and mmc_info.
> Convert printks with mmc_hostname to mmc_<level>.
>
> Whitespace neatening around pr_<level>.
> Convert printk(KERN_DEBUG to pr_debug(
> Convert direct uses of DBG macros to pr_debug.
> Convert direct uses of DBGF to DBG.
> Coalesce long format strings.
> Add a few missing newlines to logging messages.
>
> $ size drivers/mmc/built-in.o*
> text data bss dec hex filename
> 92530 1608 204 94342 17086 drivers/mmc/built-in.o.minimal.new
> 94229 1608 204 96041 17729 drivers/mmc/built-in.o.minimal.old
> 291831 5152 77344 374327 5b637 drivers/mmc/built-in.o.allyesconfig.new
> 293616 5152 78128 376896 5c040 drivers/mmc/built-in.o.allyesconfig.old
>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
> drivers/mmc/host/msm_sdcc.c | 103 +++++++++----------
Acked-by: David Brown <davidb@codeaurora.org>
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
prev parent reply other threads:[~2011-08-11 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 20:21 [PATCH] mmc: Use pr_<level>, add and use mmc_<level> Joe Perches
2011-08-11 20:34 ` David Brown [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=20110811203416.GA12740@huya.qualcomm.com \
--to=davidb@codeaurora.org \
--cc=HaraldWelte@viatech.com \
--cc=ben-linux@fluff.org \
--cc=brucechang@via.com.tw \
--cc=bryanh@codeaurora.org \
--cc=cjb@laptop.org \
--cc=dwalker@fifo99.com \
--cc=g.liakhovetski@gmx.de \
--cc=ian@mnementh.co.uk \
--cc=jarkko.lavinen@nokia.com \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=manuel.lauss@gmail.com \
--cc=nico@fluxnic.net \
--cc=nicolas.ferre@atmel.com \
--cc=oakad@yahoo.com \
--cc=pierre@ossman.eu \
--cc=ppisa@pikron.com \
--cc=tony.olech@elandigitalsystems.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