From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Dmitry Osipenko <digetx@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio <linux-iio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] iio: magnetometer: ak8974: Silence deferred-probe error
Date: Sat, 18 Apr 2020 15:26:11 +0100 [thread overview]
Message-ID: <20200418152611.1a2bf781@archlinux> (raw)
In-Reply-To: <CAHp75VdKxRGrmqPDTugVNrc3i_JDyEdJ6gmjyH=t9OiRTGg+AA@mail.gmail.com>
On Fri, 17 Apr 2020 23:50:37 +0300
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> On Fri, Apr 17, 2020 at 11:49 PM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> > On Fri, Apr 17, 2020 at 7:24 PM Dmitry Osipenko <digetx@gmail.com> wrote:
> > >
> > > It's not uncommon that voltage regulator becomes available later during
> > > kernel's boot process. This patch adds info message about unavailable
> > > regulators in a case of the deferred-probe error and also amends the
> > > error message with a error code.
> >
> >
> > > + if (ret == -EPROBE_DEFER)
> >
> > > + dev_info(&i2c->dev,
> > > + "regulators unavailable, deferring probe\n");
> >
> > I dunno why you think it is worth to spam log with this?
> > This message will be printed as many times as driver got deferred
> > probe cycle (maybe dozens in worst case).
>
> As you may see in other drivers we usually have the opposite check and
> print error message in case of != EPROBE_DEFER.
Definitely is not a good idea to print an info message for deferred.
A debug message maybe but probably not even that.
Jonathan
>
>
> >
> > > + else
> > > + dev_err(&i2c->dev, "cannot get regulators: %d\n", ret);
>
prev parent reply other threads:[~2020-04-18 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 16:22 [PATCH v2] iio: magnetometer: ak8974: Silence deferred-probe error Dmitry Osipenko
2020-04-17 20:49 ` Andy Shevchenko
2020-04-17 20:50 ` Andy Shevchenko
2020-04-18 14:26 ` Jonathan Cameron [this message]
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=20200418152611.1a2bf781@archlinux \
--to=jic23@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=digetx@gmail.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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