From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
alsa-devel@alsa-project.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] soc: fix wm0010.c printk format warning
Date: Thu, 6 Sep 2012 08:06:13 +0800 [thread overview]
Message-ID: <20120906000612.GO10580@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5047DF49.6070502@xenotime.net>
On Wed, Sep 05, 2012 at 04:24:57PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> Fix printk format warning:
Somone already sent this. As ever please try to use subject lines
appropriate for the subsystem. Please also consider who you're CCing -
there's no need to copy -next on things like this which aren't
integration issues for example, if we start doing that then it'd get
drowned in noise from all the development.
next prev parent reply other threads:[~2012-09-06 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 6:12 linux-next: Tree for Sept 5 Stephen Rothwell
2012-09-05 23:24 ` [PATCH -next] soc: fix wm0010.c printk format warning Randy Dunlap
2012-09-06 0:06 ` Mark Brown [this message]
2012-09-06 0:11 ` Randy Dunlap
2012-09-06 0:22 ` Sedat Dilek
2012-09-06 0:42 ` Mark Brown
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=20120906000612.GO10580@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).