From: Mark Brown <broonie@kernel.org>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: lgirdwood@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] drivers/regulator/core.c: Don't print error on EPROBE_DEFER
Date: Tue, 9 Dec 2014 18:48:17 +0000 [thread overview]
Message-ID: <20141209184817.GH11764@sirena.org.uk> (raw)
In-Reply-To: <54873B8E.1060106@topic.nl>
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
On Tue, Dec 09, 2014 at 07:12:30PM +0100, Mike Looijmans wrote:
> On 12/09/2014 05:14 PM, Mark Brown wrote:
> >>If a regulator depends on another regulator that happens to be called
> >>later, the kernel always prints a message like this:
> >> reg-fixed-voltage regulator_sd1: Failed to find supply vin
> >>Since the deferral is not something fatal, nor even something the user
> >>may need to be aware about, reduce the message to debug level.
> Can we instead at least reduce it to WARN or INFO level then?
You appear to have deleted my reply here... one problem with your
suggestion is that it means we have to special case all error handling
on probe for deferral which isn't wonderful.
> I have to explain over and over again that there's no problem when that
> message comes along ten times in a row. And it causes people to overlook the
> messages that really are errors.
Can we do something with the log message that triggers on probe
deferral? There tends to be a learning curve with probe deferral but
the fact that it's generally extremely noisy tends to be useful - I
usually point people at that (not just in the context at regulators) and
tell them not to worry unless debugging.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-12-09 18:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 13:12 Mike Looijmans
2014-12-09 13:12 ` [PATCH 2/2] regulator/fixed.c: Don't report EPROBE_DEFER errors Mike Looijmans
2014-12-09 16:14 ` [PATCH 1/2] drivers/regulator/core.c: Don't print error on EPROBE_DEFER Mark Brown
2014-12-09 18:12 ` Mike Looijmans
2014-12-09 18:48 ` Mark Brown [this message]
2014-12-09 19:14 ` Joe Perches
2014-12-09 19:17 ` Mark Brown
2014-12-16 10:27 ` Mike Looijmans
2014-12-16 11:29 ` 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=20141209184817.GH11764@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.looijmans@topic.nl \
/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
all inboxes | Powered by JetHome®