From: Joe Perches <joe@perches•com>
To: Nicolin Chen <nicoleotsuka@gmail•com>, Mark Brown <broonie@kernel•org>
Cc: Timur Tabi <timur@tabi•org>, Xiubo Li <Xiubo.Lee@gmail•com>,
Fabio Estevam <fabio.estevam@nxp•com>,
Krzysztof Kozlowski <krzk@kernel•org>,
Sangbeom Kim <sbkim73@samsung•com>,
Sylwester Nawrocki <s.nawrocki@samsung•com>,
Liam Girdwood <lgirdwood@gmail•com>,
Jaroslav Kysela <perex@perex•cz>, Takashi Iwai <tiwai@suse•com>,
alsa-devel@alsa-project•org, linuxppc-dev@lists•ozlabs.org,
linux-kernel@vger•kernel.org
Subject: Re: [PATCH 35/35] sound/soc: Convert remaining uses of pr_warning to pr_warn
Date: Fri, 17 Feb 2017 16:20:47 -0800 [thread overview]
Message-ID: <1487377247.2198.9.camel@perches.com> (raw)
In-Reply-To: <20170217235751.GA4125@Asurada-Nvidia>
On Fri, 2017-02-17 at 15:57 -0800, Nicolin Chen wrote:
> On Fri, Feb 17, 2017 at 11:48:54PM +0000, Mark Brown wrote:
> > On Fri, Feb 17, 2017 at 12:28:44PM -0800, Nicolin Chen wrote:
> > > On Thu, Feb 16, 2017 at 11:11:48PM -0800, Joe Perches wrote:
> > > > To enable eventual removal of pr_warning
> > > >
> > > > This makes pr_warn use consistent for sound/soc
> > > >
> > > > Prior to this patch, there were 5 uses of pr_warning and
> > > > 10 uses of pr_warn in sound/soc
> > > >
> > > > Signed-off-by: Joe Perches <joe@perches•com>
> > >
> > > For imx-audmux.c,
> >
> > I don't have this patch, perhaps it got caught in a spam filter or
> > perhaps it got deleted because as ever you're not using subject lines
> > reflecting the style for the subsystem.
>
> My bad that I didn't pay attention to the subject.
>
> Joe, please fix it in v2. Thanks.
>
> ASoC: Convert remaining uses of pr_warning to pr_warn
This is a treewide scripted patch which is
basically just a sed.
If or when you apply it, you should
fix it up to suit.
$ git log -1000 --pretty=oneline --no-merges sound/soc | \
cut -f2- -d" " | cut -f1 -d":" |sort | uniq
ALSA
AsoC
ASoc
ASoC
ASOC
ASoC fix up SND_SOC_WM8985 dependency
drm/i915/dp
kthread
lib/vsprintf.c
scripts/spelling.txt
sgtl5000
SoC
sound/soc
treewide
next prev parent reply other threads:[~2017-02-18 0:20 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 [this message]
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=1487377247.2198.9.camel@perches.com \
--to=joe@perches$(echo .)com \
--cc=Xiubo.Lee@gmail$(echo .)com \
--cc=alsa-devel@alsa-project$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=fabio.estevam@nxp$(echo .)com \
--cc=krzk@kernel$(echo .)org \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=nicoleotsuka@gmail$(echo .)com \
--cc=perex@perex$(echo .)cz \
--cc=s.nawrocki@samsung$(echo .)com \
--cc=sbkim73@samsung$(echo .)com \
--cc=timur@tabi$(echo .)org \
--cc=tiwai@suse$(echo .)com \
/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