From: Jonathan Cameron <jic23@kernel.org>
To: Peter Rosin <peda@axentia.se>
Cc: linux-kernel@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Sean Nyekjaer <sean@geanix.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Add support for texas dac121c081 to the dac5571 driver
Date: Thu, 28 Apr 2022 20:44:39 +0100 [thread overview]
Message-ID: <20220428204439.4ec2b4ae@jic23-huawei> (raw)
In-Reply-To: <42db911c-5eba-0511-3e8c-8011a2a5b44a@axentia.se>
On Mon, 25 Apr 2022 22:46:30 +0200
Peter Rosin <peda@axentia.se> wrote:
> Hi!
>
> The new chip works much like the other chips supported by the driver, so
> this is just adding another compatible to the list.
>
> Chenages since v1:
> - Guenter Roeck noticed elsewhere that my mail setup was botched and
> that my patches were clobbered. Hopefully fixed. *blush*
> - added tags from Sean Nyekjaer and Rob Herring
Applied. Thanks
Jonathan
>
> Cheers,
> Peter
>
> Peter Rosin (2):
> dt-bindings: iio: ti-dac5571: Add ti,dac121c081
> iio: dac: ti-dac5571: add support for ti,dac121c081
>
> Documentation/devicetree/bindings/iio/dac/ti,dac5571.yaml | 1 +
> drivers/iio/dac/Kconfig | 2 +-
> drivers/iio/dac/ti-dac5571.c | 3 +++
> 3 files changed, 5 insertions(+), 1 deletion(-)
>
next prev parent reply other threads:[~2022-04-28 19:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 20:46 [PATCH v2 0/2] Add support for texas dac121c081 to the dac5571 driver Peter Rosin
2022-04-25 20:46 ` [PATCH v2 1/2] dt-bindings: iio: ti-dac5571: Add ti,dac121c081 Peter Rosin
2022-04-25 20:47 ` [PATCH v2 2/2] iio: dac: ti-dac5571: add support for ti,dac121c081 Peter Rosin
2022-04-28 19:44 ` Jonathan Cameron [this message]
2022-05-01 18:03 ` [PATCH v2 0/2] Add support for texas dac121c081 to the dac5571 driver Jonathan Cameron
2022-05-12 8:59 ` Peter Rosin
2022-05-12 13:02 ` Jonathan Cameron
2022-05-22 11:57 ` 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=20220428204439.4ec2b4ae@jic23-huawei \
--to=jic23@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=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=sean@geanix.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;
as well as URLs for NNTP newsgroup(s).