From: Joe Perches <joe@perches.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Stephen Warren <swarren@nvidia.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinmux: Message logging neatening
Date: Wed, 30 Nov 2011 06:03:15 -0800 [thread overview]
Message-ID: <1322661795.2123.12.camel@Joe-Laptop> (raw)
In-Reply-To: <CACRpkdY_jYphjdZ34wHxVAY0O4rncqd_8pr_chHdr2k+zgVjBg@mail.gmail.com>
On Wed, 2011-11-30 at 14:08 +0100, Linus Walleij wrote:
> On Tue, Nov 29, 2011 at 9:05 PM, Joe Perches <joe@perches.com> wrote:
> > Coalesce formats. Argument aligning.
> > Rename pr_warning to pr_warn.
> > Add a couple missing newlines to format strings.
> I've just re-massaged much of this code in recent patches, can we save this
> cleanup for later?
Of course.
prev parent reply other threads:[~2011-11-30 14:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 20:05 Joe Perches
2011-11-30 13:08 ` Linus Walleij
2011-11-30 14:03 ` Joe Perches [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=1322661795.2123.12.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swarren@nvidia.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
all inboxes | Powered by JetHome®