From: Joe Perches <joe@perches•com>
To: Michael Ellerman <mpe@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: [PATCH 06/35] powerpc: Convert remaining uses of pr_warning to pr_warn
Date: Sun, 19 Feb 2017 20:43:19 -0800 [thread overview]
Message-ID: <1487565799.2853.1.camel@perches.com> (raw)
In-Reply-To: <87wpclh3v0.fsf@concordia.ellerman.id.au>
On Mon, 2017-02-20 at 15:40 +1100, Michael Ellerman wrote:
> Joe Perches <joe@perches•com> writes:
>
> > To enable eventual removal of pr_warning
> >
> > This makes pr_warn use consistent for arch/powerpc
> >
> > Prior to this patch, there were 36 uses of pr_warning and
> > 217 uses of pr_warn in arch/powerpc
> >
> > Signed-off-by: Joe Perches <joe@perches•com>
>
> Can I take this via the powerpc tree, or do you want to merge them as a
> series?
Well, I expect it'd be better if you merge it.
next prev parent reply other threads:[~2017-02-20 4:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 7:11 [PATCH 00/35] treewide trivial patches converting pr_warning to pr_warn Joe Perches
2017-02-17 7:11 ` [PATCH 06/35] powerpc: Convert remaining uses of " Joe Perches
2017-02-20 4:40 ` Michael Ellerman
2017-02-20 4:43 ` Joe Perches [this message]
2017-02-20 17:25 ` Geoff Levand
2017-02-17 7:11 ` [PATCH 21/35] drivers/macintosh: " Joe Perches
2017-02-17 7:11 ` [PATCH 31/35] drivers/tty: " Joe Perches
2017-02-17 7:11 ` [PATCH 35/35] sound/soc: " Joe Perches
2017-02-17 20:28 ` Nicolin Chen
2017-02-17 23:48 ` Mark Brown
2017-02-17 23:57 ` Nicolin Chen
2017-02-18 0:20 ` Joe Perches
2017-02-20 19:06 ` Mark Brown
2017-02-17 12:27 ` [PATCH 00/35] treewide trivial patches converting " Rafael J. Wysocki
2017-02-17 12:37 ` Geert Uytterhoeven
2017-02-23 15:28 ` Rob Herring
2017-02-23 17:18 ` Joe Perches
2017-02-23 17:41 ` Emil Velikov
2017-02-23 17:53 ` Joe Perches
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=1487565799.2853.1.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=mpe@ellerman$(echo .)id.au \
--cc=oss@buserror$(echo .)net \
--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