From: Jonathan Cameron <jic23@kernel.org>
To: Joshua Crofts <crofts@kernel.org>
Cc: "Chen Ni" <nichen@iscas.ac.cn>,
"Marcelo Schmitt" <marcelo.schmitt@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"David Lechner" <dlechner@baylibre.com>,
linux@analog.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Andy Shevchenko" <andriy.shevchenko@intel.com>
Subject: Re: [PATCH v2] iio: adc: ad4134: Fix duplicate data_read mux state request
Date: Sat, 7 Nov 2026 20:04:12 +0000 [thread overview]
Message-ID: <20261107200412.572956f6@jic23-hlaptop> (raw)
In-Reply-To: <20261105141846.00004e3a@kernel.org>
On Thu, 5 Nov 2026 14:18:46 +0100
Joshua Crofts <crofts@kernel.org> wrote:
> On Thu, 5 Nov 2026 11:31:20 +0800
> Chen Ni <nichen@iscas.ac.cn> wrote:
>
> > devm_mux_state_get() is called twice in a row. The second call's result
> > is stored directly into st->mux_st[AD4134_DOUT0_INPUT] without error
> > checking, and then immediately overwritten by the first call's result.
> >
> > Remove the duplicate call and check the return value before saving the
> > state.
> >
> > Fixes: f12ecb3e147b ("iio: adc: ad4134: Support SPI 4-wire mode")
> > Signed-off-by: Chen Ni <nichen@iscas.ac.cn>
>
> Ideally your Signed-off-by tag should be the last one in the tag
> block. No need to resend however, this can be tweaked when applying.
>
Applied but with fixes tag dropped. Those aren't stable until
a series has gone upstream and I've long given up on trying
to fix them up as the tree evolves.
I tweaked the ordering though I'll note I normally don't bother
too much on this as any review tags that come in after the
new posting go after the sign off anyway so it's a subtle distinction
that I'm not sure matters in practice!
Marcelo, this one looks obviously right but please take a look
just to be sure.
Jonathan
prev parent reply other threads:[~2026-11-07 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 3:31 Chen Ni
2026-11-05 13:18 ` Joshua Crofts
2026-11-07 20:04 ` 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=20261107200412.572956f6@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andriy.shevchenko@intel.com \
--cc=crofts@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@analog.com \
--cc=marcelo.schmitt@analog.com \
--cc=nichen@iscas.ac.cn \
--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
all inboxes | Powered by JetHome®