From: Mark Brown <broonie@kernel.org>
To: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 1/1] ASoC: core: Do not print an actual error when deferring probe
Date: Wed, 18 May 2016 17:21:54 +0100 [thread overview]
Message-ID: <20160518162154.GP8104@sirena.org.uk> (raw)
In-Reply-To: <1574831.WL8kGhHEjA@ws-stein>
[-- Attachment #1.1: Type: text/plain, Size: 562 bytes --]
On Wed, May 18, 2016 at 05:50:50PM +0200, Alexander Stein wrote:
> My first idea was to use dev_dbg() but that actualy remove that message at
> all, unless dynamic debug is used, so I went with dev_notice. It's still
> there, but does not clobber quiet boot log, nor some sophisticated kernel log
> parser as journalctl which prints errors in red color.
It's just shifting the problem around... it sounds like for your use
case suppressing the messages until we finish kernel boot would deal
with most of the issue in a far more general fashion.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2016-05-18 16:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 13:41 [PATCH 1/1] ASoC: core: Do not print an actual error when deferring probe Alexander Stein
2016-05-18 14:25 ` Ricard Wanderlof
2016-05-18 15:08 ` Mark Brown
2016-05-18 15:18 ` Alexander Stein
2016-05-18 15:28 ` Mark Brown
2016-05-18 15:50 ` Alexander Stein
2016-05-18 16:21 ` Mark Brown [this message]
2016-05-18 16:57 ` Takashi Iwai
2016-05-18 17:20 ` Mark Brown
2016-05-18 19:33 ` Takashi Iwai
2016-05-19 6:28 ` Alexander Stein
2016-05-19 6:53 ` Takashi Iwai
2016-05-19 10:34 ` Mark Brown
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=20160518162154.GP8104@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexander.stein@systec-electronic.com \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=tiwai@suse.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.