From: Jonathan Cameron <jic23@kernel.org>
To: Ana-Maria Cusco <anamaria.cuscoo@gmail.com>
Cc: Ana-Maria Cusco <ana-maria.cusco@analog.com>,
Lars-Peter Clausen <lars@metafoo.de>,
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>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Add ADRF5740 driver
Date: Mon, 6 Nov 2023 11:10:05 +0000 [thread overview]
Message-ID: <20231106111005.6fd278fd@jic23-huawei> (raw)
In-Reply-To: <20231103150130.1090246-1-anamaria.cuscoo@gmail.com>
On Fri, 3 Nov 2023 17:01:28 +0200
Ana-Maria Cusco <anamaria.cuscoo@gmail.com> wrote:
> From: Ana-Maria Cusco <ana-maria.cusco@analog.com>
Hi Ana-Maria,
If you do a v2, then make it clear in the title that this is adding support
to an additional driver rather than a whole new one.
>
> This patch series adds support for ADRF5740 Attenuator.
>
> The ADRF5740 is a silicon, 4-bit digital attenuator with 22 dB
> attenuation control range in 2 dB steps.
> It offers parallel control mode through four digitally controlled inputs.
>
> Ana-Maria Cusco (2):
> iio: amplifiers: adrf5740: Add Support ADRF5740 4-bit Attenuator
> dt-bindings: iio: hmc425a: add entry for ADRF5740
>
> .../bindings/iio/amplifiers/adi,hmc425a.yaml | 4 ++++
> drivers/iio/amplifiers/hmc425a.c | 23 +++++++++++++++++++
> 2 files changed, 27 insertions(+)
>
prev parent reply other threads:[~2023-11-06 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 15:01 [PATCH 0/2] Add ADRF5740 driver Ana-Maria Cusco
2023-11-03 15:01 ` [PATCH 1/2] iio: amplifiers: adrf5740: Add Support ADRF5740 4-bit Attenuator Ana-Maria Cusco
2023-11-03 15:01 ` [PATCH 2/2] dt-bindings: iio: hmc425a: add entry for ADRF5740 Ana-Maria Cusco
2023-11-05 14:05 ` Krzysztof Kozlowski
2023-11-06 11:10 ` 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=20231106111005.6fd278fd@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=ana-maria.cusco@analog.com \
--cc=anamaria.cuscoo@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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 NNTP newsgroup(s).