From: Joe Perches <joe@perches.com>
To: Mark Brown <broonie@kernel.org>
Cc: Mike Looijmans <mike.looijmans@topic.nl>,
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, 09 Dec 2014 11:14:31 -0800 [thread overview]
Message-ID: <1418152471.15957.12.camel@perches.com> (raw)
In-Reply-To: <20141209184817.GH11764@sirena.org.uk>
On Tue, 2014-12-09 at 18:48 +0000, Mark Brown wrote:
> Can we do something with the log message that triggers on probe
> deferral?
Maybe add and use rdev_err_ratelimited?
next prev parent reply other threads:[~2014-12-09 19:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 13:12 [PATCH 1/2] drivers/regulator/core.c: Don't print error on EPROBE_DEFER 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
2014-12-09 19:14 ` Joe Perches [this message]
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=1418152471.15957.12.camel@perches.com \
--to=joe@perches.com \
--cc=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