From: Joe Perches <joe@perches•com>
To: Michael Ellerman <patch-notifications@ellerman•id.au>,
Anatolij Gustschin <agust@denx•de>, Scott Wood <oss@buserror•net>,
Kumar Gala <galak@kernel•crashing.org>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>,
Paul Mackerras <paulus@samba•org>,
Geoff Levand <geoff@infradead•org>
Cc: linuxppc-dev@lists•ozlabs.org, linux-kernel@vger•kernel.org
Subject: Re: powerpc: Use pr_warn instead of pr_warning
Date: Tue, 12 Dec 2017 03:48:56 -0800 [thread overview]
Message-ID: <1513079336.3036.40.camel@perches.com> (raw)
In-Reply-To: <3ywyXQ5lPJz9sBW@ozlabs.org>
On Tue, 2017-12-12 at 22:39 +1100, Michael Ellerman wrote:
> On Tue, 2016-10-25 at 04:00:08 UTC, Joe Perches wrote:
> > At some point, pr_warning will be removed so all logging messages use
> > a consistent <prefix>_warn style.
> >
> > Update arch/powerpc/
> >
> > Miscellanea:
> >
> > o Coalesce formats
> > o Realign arguments
> > o Use %s, __func__ instead of embedded function names
> > o Remove unnecessary line continuations
> >
> > Signed-off-by: Joe Perches <joe@perches•com>
> > Acked-by: Geoff Levand <geoff@infradead•org>
>
> Applied to powerpc next, thanks.
>
> https://git.kernel.org/powerpc/c/f2c2cbcc35d47f1471a04155ac3575
OK, thanks.
But perhaps a year+ patch latency is a bit extended?
prev parent reply other threads:[~2017-12-12 11:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 4:00 [PATCH] powerpc: Use pr_warn instead of pr_warning Joe Perches
2016-10-25 16:46 ` Geoff Levand
2016-11-25 17:44 ` Joe Perches
2017-12-12 11:39 ` Michael Ellerman
2017-12-12 11:48 ` 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=1513079336.3036.40.camel@perches.com \
--to=joe@perches$(echo .)com \
--cc=agust@denx$(echo .)de \
--cc=benh@kernel$(echo .)crashing.org \
--cc=galak@kernel$(echo .)crashing.org \
--cc=geoff@infradead$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=oss@buserror$(echo .)net \
--cc=patch-notifications@ellerman$(echo .)id.au \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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