From: Jonathan Cameron <jic23@kernel.org>
To: Rodrigo Alencar <455.rodrigo.alencar@gmail.com>
Cc: Rodrigo Alencar via B4 Relay
<devnull+rodrigo.alencar.analog.com@kernel.org>,
rodrigo.alencar@analog.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
Stefan Popa <stefan.popa@analog.com>,
Jonathan Cameron <jic23@cam.ac.uk>,
Greg Kroah-Hartman <gregkh@suse.de>,
Michael Auchter <michael.auchter@ni.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
David Lechner <dlechner@baylibre.com>,
Andy Shevchenko <andy@kernel.org>,
Andy Shevchenko <andriy.shevchenko@intel.com>
Subject: Re: [PATCH 02/10] iio: dac: ad5686: remove redundant register definition
Date: Mon, 27 Apr 2026 11:25:53 +0100 [thread overview]
Message-ID: <20260427112553.6f7b598b@jic23-huawei> (raw)
In-Reply-To: <kjqs2ucnoqud3o3ilex4kostgzxhvx2xphr2akeneiwqw47q5l@veqdwbx7xzfw>
On Mon, 27 Apr 2026 11:09:59 +0100
Rodrigo Alencar <455.rodrigo.alencar@gmail.com> wrote:
> On 26/04/26 02:38PM, Jonathan Cameron wrote:
> > On Sun, 26 Apr 2026 14:32:11 +0100
> > Jonathan Cameron <jic23@kernel.org> wrote:
> >
> > > On Sun, 26 Apr 2026 09:38:03 +0100
> > > Rodrigo Alencar via B4 Relay <devnull+rodrigo.alencar.analog.com@kernel.org> wrote:
> > >
> > > > From: Rodrigo Alencar <rodrigo.alencar@analog.com>
> > > >
> > > > AD5683_REGMAP and AD5693_REGMAP behave the same way in the common code,
> > > > and that is because they target single channel devices from the same
> > > > sub-family. There is no reason to separate them and it will make things
> > > > simpler when refactoring the chip info table.
> > > >
> > > > Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> > > > Signed-off-by: Rodrigo Alencar <rodrigo.alencar@analog.com>
> > > This one stands well on it's own, so applied to the testing branch of iio.git.
> > >
> > > IIO is very busy at the moment, so I'm trying to pick up anything
> > > that is ready, including individual patches from larger series.
> > >
> > Dropped again. I didn't read on far enough. The fixes in this series
> > need to come before all this stuff so they are easier to backport.
> >
> > So dropped 2-4 from my tree pending that reorganization.
>
> I am getting the fixes first. But I still see commit 2 and 3 in the
> testing branch.
>
ah. Guess I forgot to push out. Done now (along with rebase on rc1)
next prev parent reply other threads:[~2026-04-27 10:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-26 8:38 [PATCH 00/10] Fixes and cleanups for the AD5686 IIO driver Rodrigo Alencar via B4 Relay
2026-04-26 8:38 ` [PATCH 01/10] iio: dac: ad5686: refactor include headers Rodrigo Alencar via B4 Relay
2026-04-26 13:29 ` Jonathan Cameron
2026-04-26 8:38 ` [PATCH 02/10] iio: dac: ad5686: remove redundant register definition Rodrigo Alencar via B4 Relay
2026-04-26 13:32 ` Jonathan Cameron
2026-04-26 13:38 ` Jonathan Cameron
2026-04-27 10:09 ` Rodrigo Alencar
2026-04-27 10:25 ` Jonathan Cameron [this message]
2026-04-26 8:38 ` [PATCH 03/10] iio: dac: ad5686: drop enum id Rodrigo Alencar via B4 Relay
2026-04-26 13:35 ` Jonathan Cameron
2026-04-26 8:38 ` [PATCH 04/10] iio: dac: ad5686: add of_match table to the spi driver Rodrigo Alencar via B4 Relay
2026-04-26 13:37 ` Jonathan Cameron
2026-04-26 8:38 ` [PATCH 05/10] iio: dac: ad5686: fix ref bit initialization for single-channel parts Rodrigo Alencar via B4 Relay
2026-04-26 13:44 ` Jonathan Cameron
2026-04-26 8:38 ` [PATCH 06/10] iio: dac: ad5686: acquire lock when doing powerdown control Rodrigo Alencar via B4 Relay
2026-04-26 13:47 ` Jonathan Cameron
2026-04-26 8:38 ` [PATCH 07/10] iio: dac: ad5686: fix powerdown control on dual-channel devices Rodrigo Alencar via B4 Relay
2026-04-26 13:48 ` Jonathan Cameron
2026-04-26 8:38 ` [PATCH 08/10] iio: dac: ad5686: fix input raw value check Rodrigo Alencar via B4 Relay
2026-04-26 13:49 ` Jonathan Cameron
2026-04-26 8:38 ` [PATCH 09/10] iio: dac: ad5686: cleanup doc header of local structs Rodrigo Alencar via B4 Relay
2026-04-26 8:38 ` [PATCH 10/10] iio: dac: ad5686: create bus ops struct Rodrigo Alencar via B4 Relay
2026-04-26 13:50 ` Jonathan Cameron
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=20260427112553.6f7b598b@jic23-huawei \
--to=jic23@kernel.org \
--cc=455.rodrigo.alencar@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=devnull+rodrigo.alencar.analog.com@kernel.org \
--cc=dlechner@baylibre.com \
--cc=gregkh@suse.de \
--cc=jic23@cam.ac.uk \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.auchter@ni.com \
--cc=rodrigo.alencar@analog.com \
--cc=stefan.popa@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