From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Randy Dunlap <rdunlap@xenotime.net>
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: Thu, 6 Sep 2012 08:42:57 +0800 [thread overview]
Message-ID: <20120906004251.GV10580@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5047EA1C.7080608@xenotime.net>
On Wed, Sep 05, 2012 at 05:11:08PM -0700, Randy Dunlap wrote:
> On 09/05/2012 05:06 PM, Mark Brown wrote:
> > 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?
As with every other subsystem in the kernel look at the log for the
thing your changing and do something that visually resembles it. If you
want get_maintainers to do this for you you'll need to write the code
(or convince someone else to do it).
> > 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).
I'm pretty sure I've mentioned this before... actually, if you're
relying on get_maintainers that's probably some of the false positives
too. If you've found an issue related to the -next integration that's
one thing but if you've just noticed a random thing in the kernel that
could be improved that's not really something about -next.
prev parent reply other threads:[~2012-09-06 0:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120905161230.3bab1de6d4c8c8e466c3b0df@canb.auug.org.au>
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
2012-09-06 0:22 ` Sedat Dilek
2012-09-06 0:42 ` Mark Brown [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=20120906004251.GV10580@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).