From: David Lechner <dlechner@baylibre.com>
To: Marcelo Schmitt <marcelo.schmitt@analog.com>,
linux-iio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: jic23@kernel.org, lars@metafoo.de, Michael.Hennerich@analog.com,
corbet@lwn.net, marcelo.schmitt1@gmail.com
Subject: Re: [PATCH v2 3/5] Documentation: iio: ad4000: Add new supported parts
Date: Thu, 20 Mar 2025 15:47:52 -0500 [thread overview]
Message-ID: <1b544061-4b5c-4a69-98c3-265f9d1e32ec@baylibre.com> (raw)
In-Reply-To: <4ad6c3d6dbfac9d5e9321a23a647cf333d7f96b6.1742394806.git.marcelo.schmitt@analog.com>
On 3/19/25 9:57 AM, Marcelo Schmitt wrote:
> Commit <c3948d090080> ("iio: adc: ad4000: Add support for PulSAR devices"),
> extended the ad4000 driver supports many single-channel PulSAR devices.
>
> Update IIO ad4000 documentation with the extra list of supported devices.
>
> Signed-off-by: Marcelo Schmitt <marcelo.schmitt@analog.com>
> ---
Reviewed-by: David Lechner <dlechner@baylibre.com>
next prev parent reply other threads:[~2025-03-20 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 14:56 [PATCH v2 0/5] iio: adc: ad4000: Add SPI offload support Marcelo Schmitt
2025-03-19 14:57 ` [PATCH v2 1/5] iio: adc: ad400: Set transfer bits_per_word to have data in CPU endianness Marcelo Schmitt
2025-03-20 20:43 ` David Lechner
2025-03-21 19:07 ` Marcelo Schmitt
2025-03-19 14:57 ` [PATCH v2 2/5] iio: adc: ad4000: Add support for SPI offload Marcelo Schmitt
2025-03-20 20:47 ` David Lechner
2025-03-21 19:54 ` Marcelo Schmitt
2025-03-21 20:11 ` David Lechner
2025-03-19 14:57 ` [PATCH v2 3/5] Documentation: iio: ad4000: Add new supported parts Marcelo Schmitt
2025-03-20 20:47 ` David Lechner [this message]
2025-03-19 14:57 ` [PATCH v2 4/5] Documentation: iio: ad4000: Add IIO Device characteristics section Marcelo Schmitt
2025-03-20 20:47 ` David Lechner
2025-03-19 14:58 ` [PATCH v2 5/5] Documentation: iio: ad4000: Describe offload support Marcelo Schmitt
2025-03-20 20:48 ` David Lechner
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=1b544061-4b5c-4a69-98c3-265f9d1e32ec@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Michael.Hennerich@analog.com \
--cc=corbet@lwn.net \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=marcelo.schmitt@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