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, Liam Girdwood <lrg@ti.com>,
moderated for non-subscribers <alsa-devel@alsa-project.org>
Subject: Re: [PATCH -next] ASoC: fix wm2200.c printk format warnings
Date: Mon, 22 Oct 2012 14:39:56 +0100 [thread overview]
Message-ID: <20121022133956.GH4477@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5081DE83.2060402@xenotime.net>
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
On Fri, Oct 19, 2012 at 04:13:07PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> Fix wm2200.c printk format warnings (seen on x86_64):
Applied but it is very depressing that I need to *again* remind you to
pay attention to where you're sending patches:
- *ALWAYS* send patches to the maintainers.
- Don't send patches to irrelevant people/lists.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-10-22 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121019135419.f996aed8ed85ee50a782a649@canb.auug.org.au>
2012-10-19 23:13 ` [PATCH -next] ASoC: fix wm2200.c printk format warnings Randy Dunlap
2012-10-22 13:39 ` 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=20121022133956.GH4477@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@ti.com \
--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).