From: Randy Dunlap <randy.dunlap@oracle.com>
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>
Subject: Re: [PATCH -next] soc: fix wm8958-dsp2 printk format warnings
Date: Sun, 08 May 2011 08:38:31 -0700 [thread overview]
Message-ID: <4DC6B8F7.4000302@oracle.com> (raw)
In-Reply-To: <20110508140101.GB15968@opensource.wolfsonmicro.com>
On 05/08/11 07:01, Mark Brown wrote:
> On Fri, May 06, 2011 at 04:13:10PM -0700, Randy Dunlap wrote:
>> From: Randy Dunlap <randy.dunlap@oracle.com>
>>
>> Fix printk format warnings in wm8958-dsp2.c:
>
> Please do try to follow the standard patch submission process:
>
> - Send patches to maintainers.
> - Send patches to the relevant mailing lists.
> - Use the relevant subsystem prefix in your commit message.
OK, I will note this and save this email for future reference.
Do I need to resend the patch?
What subsystem prefix do you want to see there? from MAINTAINERS file:
SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEMENT (ASoC)
thanks,
--
~Randy
next prev parent reply other threads:[~2011-05-08 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 3:49 linux-next: Tree for May 5 Stephen Rothwell
2011-05-06 23:13 ` [PATCH -next] soc: fix wm8958-dsp2 printk format warnings Randy Dunlap
2011-05-08 14:01 ` Mark Brown
2011-05-08 15:38 ` Randy Dunlap [this message]
2011-05-08 16:06 ` Mark Brown
2011-05-08 16:48 ` [PATCH -next] ASoC: " Randy Dunlap
2011-05-11 14:05 ` Liam Girdwood
2011-05-11 16:16 ` Mark Brown
2011-05-07 3:24 ` linux-next: Tree for May 5 Jean-Christophe PLAGNIOL-VILLARD
2011-05-09 5:54 ` Stephen Rothwell
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=4DC6B8F7.4000302@oracle.com \
--to=randy.dunlap@oracle.com \
--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).