From: Sekhar Nori <nsekhar@ti.com>
To: Joe Perches <joe@perches.com>,
Kevin Hilman <khilman@deeprootsystems.com>
Cc: Russell King <linux@arm.linux.org.uk>,
<davinci-linux-open-source@linux.davincidsp.com>,
<linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] davinci: Use standard logging styles
Date: Tue, 18 Nov 2014 21:08:29 +0530 [thread overview]
Message-ID: <546B67F5.20108@ti.com> (raw)
In-Reply-To: <1414803111.13647.13.camel@perches.com>
On Saturday 01 November 2014 06:21 AM, Joe Perches wrote:
> Convert printks to pr_<level> and pr_warning to pr_warn.
>
> Other miscellanea:
>
> o Coalesce formats
> o Realign arguments
> o Use %s, __func__ instead of embedded function names
> o Add pr_fmt to mityomapl138 and mux
>
> Signed-off-by: Joe Perches <joe@perches.com>
Sending to ARM-SoC for v3.19. Prefixed subject line with ARM: as is the
convention.
Thanks,
Sekhar
prev parent reply other threads:[~2014-11-18 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 0:51 [PATCH] davinci: Use standard logging styles Joe Perches
2014-11-18 15:38 ` Sekhar Nori [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=546B67F5.20108@ti.com \
--to=nsekhar@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=joe@perches.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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