From: Ladislav Michl <ladis@linux-mips.org>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] sound: soc-core: make kernel complaints on -EPROBE_DEFER dev_dbg
Date: Wed, 9 Nov 2016 16:14:26 +0100 [thread overview]
Message-ID: <20161109151426.GA21280@localhost.localdomain> (raw)
In-Reply-To: <20161109143642.7knvr63vwmcgunjf@sirena.org.uk>
On Wed, Nov 09, 2016 at 02:36:42PM +0000, Mark Brown wrote:
> On Wed, Nov 09, 2016 at 03:00:36PM +0100, Ladislav Michl wrote:
> > There is no point having these complaints to be dev_err as
> > they are just adding noise to bootlog.
>
> No, errors are errors and not displaying them just makes it harder for
> people to debug things. If you don't want to see errors just change
> your system configuratiion to hide them.
For sure I want to see all errors, but this is not hardware error nor
kernel misconfiguration, so showing it to the user is a bit pointless.
I'm using quiet boot on production systems and technicians are told
to report all errors they see... This one pops up and has nothing
to do with errorneous behaviour.
> If you don't like deferred probing please contribute to the efforts
> to order probing.
I just tried to make it consistend to other subsystems where patches to
silence deferred probing warnings are accepted...
> Please use subject lines matching the style for the subsystem. This
> makes it easier for people to identify relevant patches.
I wasn't aware of it, sorry. Will fix it next time.
Best regards,
ladis
next prev parent reply other threads:[~2016-11-09 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 14:00 [PATCH] sound: soc-core: make kernel complaints on -EPROBE_DEFER dev_dbg Ladislav Michl
2016-11-09 14:36 ` Mark Brown
2016-11-09 15:14 ` Ladislav Michl [this message]
2016-11-09 15:22 ` Mark Brown
2016-11-09 16:36 ` Ladislav Michl
2016-11-12 10:00 ` 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=20161109151426.GA21280@localhost.localdomain \
--to=ladis@linux-mips.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.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 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).