From: Joe Perches <joe@perches•com>
To: Rob Herring <robh@kernel•org>
Cc: Alexander Shishkin <alexander.shishkin@linux•intel.com>,
Karol Herbst <karolherbst@gmail•com>,
Pekka Paalanen <ppaalanen@gmail•com>,
Richard Weinberger <richard@nod•at>,
Fabio Estevam <fabio.estevam@nxp•com>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"linux-arm-kernel@lists•infradead.org"
<linux-arm-kernel@lists•infradead.org>,
linuxppc-dev <linuxppc-dev@lists•ozlabs.org>,
tboot-devel@lists•sourceforge.net, nouveau@lists•freedesktop.org,
oprofile-list@lists•sf.net, sfi-devel@simplefirmware•org,
xen-devel@lists•xenproject.org,
"linux-acpi@vger•kernel.org" <linux-acpi@vger•kernel.org>,
drbd-dev@lists•linbit.com,
virtualization@lists•linux-foundation.org,
linux-crypto@vger•kernel.org,
"linux-ide@vger•kernel.org" <linux-ide@vger•kernel.org>,
gigaset307x-common@lists•sourceforge.net,
"linux-media@vger•kernel.org" <linux-media@vger•kernel.org>,
linux-omap <linux-omap@vger•kernel.org>,
"linux-mtd@lists•infradead.org" <linux-mtd@lists•infradead.org>,
"devicetree@vger•kernel.org" <devicetree@vger•kernel.org>,
acpi4asus-user@lists•sourceforge.net,
platform-driver-x86@vger•kernel.org, linux-scsi@vger•kernel.org,
"linux-fbdev@vger•kernel.org" <linux-fbdev@vger•kernel.org>,
Linux-ALSA <alsa-devel@alsa-project•org>,
linux-alpha@vger•kernel.org,
adi-buildroot-devel@lists•sourceforge.net,
linux-ia64@vger•kernel.org, SH-Linux <linux-sh@vger•kernel.org>,
sparclinux@vger•kernel.org, amd-gfx@lists•freedesktop.org,
dri-devel <dri-devel@lists•freedesktop.org>,
"linux-input@vger•kernel.org" <linux-input@vger•kernel.org>,
netdev <netdev@vger•kernel.org>
Subject: Re: [PATCH 00/35] treewide trivial patches converting pr_warning to pr_warn
Date: Thu, 23 Feb 2017 09:18:24 -0800 [thread overview]
Message-ID: <1487870304.14159.29.camel@perches.com> (raw)
In-Reply-To: <CAL_JsqLTaq-QLTqfyDO8EVJYpgeUx1e4J0Fo2NvfFWqVoiVedQ@mail.gmail.com>
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.
next prev parent reply other threads:[~2017-02-23 17:18 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
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 [this message]
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=1487870304.14159.29.camel@perches.com \
--to=joe@perches$(echo .)com \
--cc=acpi4asus-user@lists$(echo .)sourceforge.net \
--cc=adi-buildroot-devel@lists$(echo .)sourceforge.net \
--cc=alexander.shishkin@linux$(echo .)intel.com \
--cc=alsa-devel@alsa-project$(echo .)org \
--cc=amd-gfx@lists$(echo .)freedesktop.org \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=drbd-dev@lists$(echo .)linbit.com \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=fabio.estevam@nxp$(echo .)com \
--cc=gigaset307x-common@lists$(echo .)sourceforge.net \
--cc=karolherbst@gmail$(echo .)com \
--cc=linux-acpi@vger$(echo .)kernel.org \
--cc=linux-alpha@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-crypto@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-input@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-media@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=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nouveau@lists$(echo .)freedesktop.org \
--cc=oprofile-list@lists$(echo .)sf.net \
--cc=platform-driver-x86@vger$(echo .)kernel.org \
--cc=ppaalanen@gmail$(echo .)com \
--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 \
--cc=xen-devel@lists$(echo .)xenproject.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