From: Randy Dunlap <rdunlap@xenotime.net>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH -next] soc: fix wm0010.c printk format warning
Date: Wed, 05 Sep 2012 17:11:08 -0700 [thread overview]
Message-ID: <5047EA1C.7080608@xenotime.net> (raw)
In-Reply-To: <20120906000612.GO10580@opensource.wolfsonmicro.com>
On 09/05/2012 05:06 PM, Mark Brown wrote:
> 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 -
Unfortunately the MAINTAINERS file does not tell me what to include
in the $subject line for the subsystem.
What would you like to see there, please? Maybe ASoC?
> there's no need to copy -next on things like this which aren't
I have always done a reply-to-all for linux-next patches, so after
a few years someone days Don't Do That (IYO).
> integration issues for example, if we start doing that then it'd get
> drowned in noise from all the development.
Agreed, many of us are already drowning from 1000+ emails per day.
(seriously)
--
~Randy
next prev parent reply other threads:[~2012-09-06 0:11 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
2012-09-06 0:11 ` Randy Dunlap [this message]
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=5047EA1C.7080608@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).