The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Maxwell Doose <m32285159@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"open list:IIO SUBSYSTEM AND DRIVERS" <linux-iio@vger.kernel.org>,
	"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] iio: chemical: scd30: Use devm_mutex_init() over non-devm mutex_init()
Date: Fri, 5 Jun 2026 12:59:29 +0100	[thread overview]
Message-ID: <20260605125929.2082dfc2@jic23-huawei> (raw)
In-Reply-To: <CAKqfh0FU5g96PjcXcz_hPafZR2uLq3xX2V-yyraHqPXX8RBRDw@mail.gmail.com>

On Thu, 4 Jun 2026 11:21:07 -0500
Maxwell Doose <m32285159@gmail.com> wrote:

> On Thu, Jun 4, 2026 at 11:20 AM David Lechner <dlechner@baylibre.com> wrote:
> >
> > On Thu, Jun 4, 2026 at 3:17 PM Maxwell Doose <m32285159@gmail.com> wrote:  
> > >
> > > The current code uses mutex_init() instead of devm_mutex_init(), which
> > > is incorrect as the rest of the file uses the devm automatic resource
> > > management API. Fix this so that the mutex is set up in the same way as
> > > the rest of the device data structure.
> > >
> > > Signed-off-by: Maxwell Doose <m32285159@gmail.com>
> > > ---
> > >  v2:
> > >  - Drop fixes tag per Jonathan's suggestion.
> > >  - Replace dev_err_probe() with return -ENOMEM per Jonathan and Andy's
> > >    suggestions.
> > >
> > >  drivers/iio/chemical/scd30_core.c | 5 ++++-
> > >  1 file changed, 4 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/iio/chemical/scd30_core.c b/drivers/iio/chemical/scd30_core.c
> > > index db5cc295aeab..198add58affd 100644
> > > --- a/drivers/iio/chemical/scd30_core.c
> > > +++ b/drivers/iio/chemical/scd30_core.c
> > > @@ -714,7 +714,10 @@ int scd30_probe(struct device *dev, int irq, const char *name, void *priv,
> > >         state->pressure_comp = SCD30_PRESSURE_COMP_DEFAULT;
> > >         state->meas_interval = SCD30_MEAS_INTERVAL_DEFAULT;
> > >         state->command = command;
> > > -       mutex_init(&state->lock);
> > > +       ret = devm_mutex_init(dev, &state->lock);
> > > +       if (ret)
> > > +               return -ENOMEM;  
> >
> > Why are we ignoring ret?
> >
> > I would expect:
> >
> >               return ret;
> >  
> 
> Gah, I must've Jonathan's + Andy's comments get to my head (He said it
> should likely only return -ENOMEM) :(
> I don't know if he'll want to tweak while applying or if I should just
> go back and resubmit.

IIO is effectively closed for this cycle so plenty of time and I'm lazy
so please send a v3.

Jonathan

      parent reply	other threads:[~2026-06-05 11:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04 13:15 [PATCH v2] iio: chemical: scd30: Use devm_mutex_init() over non-devm mutex_init() Maxwell Doose
2026-06-04 13:50 ` Joshua Crofts
2026-06-04 16:19 ` David Lechner
2026-06-04 16:21   ` Maxwell Doose
2026-06-04 20:58     ` Andy Shevchenko
2026-06-05 11:59     ` 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=20260605125929.2082dfc2@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m32285159@gmail.com \
    --cc=nuno.sa@analog.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