From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: linux-iio@vger.kernel.org,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH v5 0/2] iio: adc: ad7944: new driver
Date: Sun, 10 Mar 2024 15:20:29 +0000 [thread overview]
Message-ID: <20240310152029.6f9cc8e8@jic23-huawei> (raw)
In-Reply-To: <20240304-ad7944-mainline-v5-0-f0a38cea8901@baylibre.com>
On Mon, 4 Mar 2024 13:48:45 -0600
David Lechner <dlechner@baylibre.com> wrote:
> This is a new driver for the Analog Devices AD7944/AD7985/AD7986 family
> of ADCs. These are fairly simple chips (e.g. no configuration registers)
> but do have some unusual SPI configurations. The initial driver is only
> supporting the normal (4-wire) SPI mode.
>
> This work is done on behalf of Analog Devices, Inc., hence the
> MAINTAINERS are @analog.com folks.
Series applied to the togreg-normal branch of iio.git and pushed out
for 0-day to get a head start. This is now 6.10 material given timing.
I'll be rebasing my tree after rc1 at which point I'll fall back to my normal
togreg branch naming.
Thanks,
Jonathan
prev parent reply other threads:[~2024-03-10 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 19:48 [PATCH v5 0/2] iio: adc: ad7944: new driver David Lechner
2024-03-04 19:48 ` [PATCH v5 1/2] dt-bindings: iio: adc: add ad7944 ADCs David Lechner
2024-03-04 19:48 ` [PATCH v5 2/2] iio: adc: ad7944: add driver for AD7944/AD7985/AD7986 David Lechner
2024-03-06 10:22 ` Nuno Sá
2024-03-10 15:20 ` 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=20240310152029.6f9cc8e8@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).