The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Christian Eggers <ceggers@arri.de>
To: Doug Anderson <dianders@chromium.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, <linux-kernel@vger.kernel.org>,
	<stable@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] regulator: check that dummy regulator has been probed before using it
Date: Thu, 13 Mar 2025 08:40:34 +0100	[thread overview]
Message-ID: <2729466.lGaqSPkdTl@n9w6sw14> (raw)
In-Reply-To: <CAD=FV=V9WRjcxfYRtBWUe+twqjqkmW4r_oZYo2xJ4PctXgBQxw@mail.gmail.com>

On Thursday, 13 March 2025, 01:46:43 CET, Doug Anderson wrote:
> Hi,
> 
> On Tue, Mar 11, 2025 at 2:18 AM Christian Eggers <ceggers@arri.de> wrote:
> >
> > @@ -2213,6 +2221,8 @@ struct regulator *_regulator_get_common(struct regulator_dev *rdev, struct devic
> >                          */
> >                         dev_warn(dev, "supply %s not found, using dummy regulator\n", id);
> >                         rdev = dummy_regulator_rdev;
> > +                       if (!rdev)
> > +                               return ERR_PTR(-EPROBE_DEFER);
> 
> nit: it feels like the dev_warn() above should be below your new
> check. Otherwise you'll get the same message again after the deferral
> processes.
> 

I actually had a similar feeling during making the change.  Having entropy on warning
messages isn't very nice, so I'll send a v3.

regards
Christian




  reply	other threads:[~2025-03-13  7:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11  9:18 [PATCH v2 1/2] regulator: dummy: force synchronous probing Christian Eggers
2025-03-11  9:18 ` [PATCH v2 2/2] regulator: check that dummy regulator has been probed before using it Christian Eggers
2025-03-13  0:46   ` Doug Anderson
2025-03-13  7:40     ` Christian Eggers [this message]
2025-03-11 19:17 ` [PATCH v2 1/2] regulator: dummy: force synchronous probing Mark Brown
2025-03-13  0:42 ` Doug Anderson
2025-03-13  7:36   ` Christian Eggers

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=2729466.lGaqSPkdTl@n9w6sw14 \
    --to=ceggers@arri.de \
    --cc=broonie@kernel.org \
    --cc=dianders@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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