From: David Lechner <dlechner@baylibre.com>
To: Stefano Manni <stefano.manni@gmail.com>,
lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
nuno.sa@analog.com, andy@kernel.org
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] iio: adc: ad799x: reference voltage capability
Date: Wed, 6 Aug 2025 10:40:28 -0500 [thread overview]
Message-ID: <29bac7ef-c9b2-4e37-b4a9-08a0120e6083@baylibre.com> (raw)
In-Reply-To: <20250806090158.117628-1-stefano.manni@gmail.com>
On 8/6/25 4:01 AM, Stefano Manni wrote:
> This patch series refactors 6b104e7895ab16b9b7f466c5f2ca282b87f661e8
> in order to add the capability of the chip to have an
> external reference voltage into the chip_info struct.
> And so avoid ugly conditional checks on the chip id.
>
> In addition the AD7994 is marked to have the external
> reference voltage as well.
>
> Stefano Manni (2):
> iio: adc: ad799x: add reference voltage capability to chip_info
> iio: adc: ad799x: add reference voltage to ad7994
>
> drivers/iio/adc/ad799x.c | 45 +++++++++++++++++++++++-----------------
> 1 file changed, 26 insertions(+), 19 deletions(-)
>
Something to keep in mind if you send more patches: this
should have been [PATCH v2] with a link to (implicit) v1 [1].
[1]: https://lore.kernel.org/linux-iio/20250805142423.17710-1-stefano.manni@gmail.com/
next prev parent reply other threads:[~2025-08-06 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 9:01 Stefano Manni
2025-08-06 9:01 ` [PATCH 1/2] iio: adc: ad799x: add reference voltage capability to chip_info Stefano Manni
2025-08-06 14:58 ` Jonathan Cameron
2025-08-06 15:36 ` David Lechner
2025-08-06 20:15 ` Andy Shevchenko
2025-08-06 9:01 ` [PATCH 2/2] iio: adc: ad799x: add reference voltage to ad7994 Stefano Manni
2025-08-06 20:16 ` Andy Shevchenko
2025-08-06 15:40 ` David Lechner [this message]
2025-08-06 20:06 ` [PATCH 0/2] iio: adc: ad799x: reference voltage capability Andy Shevchenko
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=29bac7ef-c9b2-4e37-b4a9-08a0120e6083@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=stefano.manni@gmail.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®