From: Joe Perches <joe@perches•com>
To: Emil Velikov <emil.l.velikov@gmail•com>
Cc: "linux-fbdev@vger•kernel.org" <linux-fbdev@vger•kernel.org>,
linux-ia64@vger•kernel.org, SH-Linux <linux-sh@vger•kernel.org>,
Alexander Shishkin <alexander.shishkin@linux•intel.com>,
ML nouveau <nouveau@lists•freedesktop.org>,
Linux-ALSA <alsa-devel@alsa-project•org>,
dri-devel <dri-devel@lists•freedesktop.org>,
"open list:VIRTIO GPU DRIVER"
<virtualization@lists•linux-foundation.org>,
"linux-ide@vger•kernel.org" <linux-ide@vger•kernel.org>,
"linux-mtd@lists•infradead.org" <linux-mtd@lists•infradead.org>,
sparclinux@vger•kernel.org, drbd-dev@lists•linbit.com,
Rob Herring <robh@kernel•org>,
linux-omap <linux-omap@vger•kernel.org>,
linux-scsi@vger•kernel.org, Richard Weinberger <richard@nod•at>,
tboot-devel@lists•sourceforge.net,
amd-gfx mailing list <amd-gfx@lists•freedesktop.org>,
"linux-acpi@vger•kernel.org" <linux-acpi@vger•kernel.org>,
sfi-devel@simplefirmware•org,
Subject: Re: [PATCH 00/35] treewide trivial patches converting pr_warning to pr_warn
Date: Thu, 23 Feb 2017 09:53:41 -0800 [thread overview]
Message-ID: <1487872421.14159.38.camel@perches.com> (raw)
In-Reply-To: <CACvgo50LUm5VSn_F=Dh8kL5zCPpCQDoCyUEL=Z+=1+6hJpfTaw@mail.gmail.com>
On Thu, 2017-02-23 at 17:41 +0000, Emil Velikov wrote:
> On 23 February 2017 at 17:18, Joe Perches <joe@perches•com> wrote:
> > On Thu, 2017-02-23 at 09:28 -0600, Rob Herring wrote:
> > > On Fri, Feb 17, 2017 at 1:11 AM, Joe Perches <joe@perches•com> wrote:
> > > > There are ~4300 uses of pr_warn and ~250 uses of the older
> > > > pr_warning in the kernel source tree.
> > > >
> > > > Make the use of pr_warn consistent across all kernel files.
> > > >
> > > > This excludes all files in tools/ as there is a separate
> > > > define pr_warning for that directory tree and pr_warn is
> > > > not used in tools/.
> > > >
> > > > Done with 'sed s/\bpr_warning\b/pr_warn/' and some emacsing.
> >
> > []
> > > Where's the removal of pr_warning so we don't have more sneak in?
> >
> > After all of these actually get applied,
> > and maybe a cycle or two later, one would
> > get sent.
> >
>
> By which point you'll get a few reincarnation of it. So you'll have to
> do the same exercise again :-(
Maybe to one or two files. Not a big deal.
> I guess the question is - are you expecting to get the series merged
> all together/via one tree ?
No. The only person that could do that effectively is Linus.
> If not, your plan is perfectly reasonable.
prev parent reply other threads:[~2017-02-23 17:53 UTC|newest]
Thread overview: 9+ 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 20/35] drivers/isdn: Convert remaining uses of " Joe Perches
2017-02-17 8:49 ` Paul Bolle
[not found] ` <cover.1487314666.git.joe-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
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 [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=1487872421.14159.38.camel@perches.com \
--to=joe@perches$(echo .)com \
--cc=alexander.shishkin@linux$(echo .)intel.com \
--cc=alsa-devel@alsa-project$(echo .)org \
--cc=amd-gfx@lists$(echo .)freedesktop.org \
--cc=drbd-dev@lists$(echo .)linbit.com \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=emil.l.velikov@gmail$(echo .)com \
--cc=linux-acpi@vger$(echo .)kernel.org \
--cc=linux-fbdev@vger$(echo .)kernel.org \
--cc=linux-ia64@vger$(echo .)kernel.org \
--cc=linux-ide@vger$(echo .)kernel.org \
--cc=linux-mtd@lists$(echo .)infradead.org \
--cc=linux-omap@vger$(echo .)kernel.org \
--cc=linux-scsi@vger$(echo .)kernel.org \
--cc=linux-sh@vger$(echo .)kernel.org \
--cc=nouveau@lists$(echo .)freedesktop.org \
--cc=richard@nod$(echo .)at \
--cc=robh@kernel$(echo .)org \
--cc=sfi-devel@simplefirmware$(echo .)org \
--cc=sparclinux@vger$(echo .)kernel.org \
--cc=tboot-devel@lists$(echo .)sourceforge.net \
--cc=virtualization@lists$(echo .)linux-foundation.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