From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: omap: Remove needless prints from machine drivers
Date: Wed, 6 Oct 2010 08:43:34 -0700 [thread overview]
Message-ID: <20101006154334.GD2803@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1286372846-10238-1-git-send-email-jhnikula@gmail.com>
On Wed, Oct 06, 2010 at 04:47:26PM +0300, Jarkko Nikula wrote:
> It is currently completely normal to execute these machine drivers code on
> different boards if the kernel includes support for multiple boards so no
> error message should be printed if the machine_is_xxx does not match with
> the machine driver.
>
> Therefore remove these pr_err and pr_debug prints in those cases.
>
> Signed-off-by: Jarkko Nikula <jhnikula@gmail.com>
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
next prev parent reply other threads:[~2010-10-06 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 13:47 [PATCH] ASoC: omap: Remove needless prints from machine drivers Jarkko Nikula
2010-10-06 15:43 ` Mark Brown [this message]
2010-10-10 10:37 ` Liam Girdwood
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=20101006154334.GD2803@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jhnikula@gmail.com \
--cc=lrg@slimlogic.co.uk \
/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