From: Conor Dooley <conor@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/6] dt-bindings: iio: adc: adi,ad4080: add support for AD4082
Date: Fri, 13 Feb 2026 18:12:38 +0000 [thread overview]
Message-ID: <20260213-tipoff-risk-2f2256160981@spud> (raw)
In-Reply-To: <20260213144629.16001-2-antoniu.miclaus@analog.com>
[-- Attachment #1: Type: text/plain, Size: 75 bytes --]
Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: not-applicable
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-02-13 18:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 14:46 [PATCH v2 0/6] iio: adc: ad4080: add support for AD4082, AD4085 and AD4088 Antoniu Miclaus
2026-02-13 14:46 ` [PATCH v2 1/6] dt-bindings: iio: adc: adi,ad4080: add support for AD4082 Antoniu Miclaus
2026-02-13 18:12 ` Conor Dooley [this message]
2026-02-14 8:52 ` Krzysztof Kozlowski
2026-02-13 14:46 ` [PATCH v2 2/6] iio: adc: ad4080: " Antoniu Miclaus
2026-02-13 14:46 ` [PATCH v2 3/6] dt-bindings: iio: adc: adi,ad4080: add support for AD4085 Antoniu Miclaus
2026-02-13 18:15 ` Conor Dooley
2026-02-14 8:51 ` Krzysztof Kozlowski
2026-02-13 14:46 ` [PATCH v2 4/6] iio: adc: ad4080: " Antoniu Miclaus
2026-02-13 14:46 ` [PATCH v2 5/6] dt-bindings: iio: adc: adi,ad4080: add support for AD4088 Antoniu Miclaus
2026-02-13 18:16 ` Conor Dooley
2026-02-14 8:52 ` Krzysztof Kozlowski
2026-02-13 14:46 ` [PATCH v2 6/6] iio: adc: ad4080: " Antoniu Miclaus
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=20260213-tipoff-risk-2f2256160981@spud \
--to=conor@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--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