From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@ti.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH v2] ASoC: DAPM - Use dev_warn for debugfs warning message.
Date: Tue, 6 Mar 2012 20:08:11 +0000 [thread overview]
Message-ID: <20120306200810.GC19635@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1331057605-4542-1-git-send-email-lrg@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 312 bytes --]
On Tue, Mar 06, 2012 at 06:13:25PM +0000, Liam Girdwood wrote:
> Remove printk(KERN_WARNING) and use dev_warn() instead.
Applied, thanks.
Everyone else seems to be doing ASoC: thing: rather than having a -. As
far as I remember it was Peter that started it, though other people
(including me) adopted it too.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-03-06 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 18:13 [PATCH v2] ASoC: DAPM - Use dev_warn for debugfs warning message Liam Girdwood
2012-03-06 20:08 ` Mark Brown [this message]
2012-03-07 9:48 ` Liam Girdwood
2012-03-07 12:07 ` Mark Brown
2012-03-07 12:59 ` Takashi Iwai
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=20120306200810.GC19635@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.