mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"David Lechner" <dlechner@baylibre.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	linux@analog.com, linux-iio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] iio: adc: ad4080: add support for AD4884
Date: Fri, 29 May 2026 18:15:42 +0100	[thread overview]
Message-ID: <20260529181542.7df3bbc5@jic23-huawei> (raw)
In-Reply-To: <20260529141353.8492-1-antoniu.miclaus@analog.com>

On Fri, 29 May 2026 17:13:51 +0300
Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:

> Add support for the AD4884, a dual-channel, 16-bit, 40 MSPS SAR ADC,
> to the ad4080 driver family.
> 
> Patch 1 adds the AD4884 compatible string to the devicetree binding.
> Patch 2 adds the chip info and device ID to the driver.
> 
> Changes in v2:
> - Add rationale for no fallback compatible in commit message.
> - Collect Acked-by tag.
> 
Applied

Thanks,

J
> Antoniu Miclaus (2):
>   dt-bindings: iio: adc: ad4080: add AD4884 support
>   iio: adc: ad4080: add support for AD4884
> 
>  .../bindings/iio/adc/adi,ad4080.yaml           |  5 ++++-
>  drivers/iio/adc/ad4080.c                       | 18 ++++++++++++++++++
>  2 files changed, 22 insertions(+), 1 deletion(-)
> 


      parent reply	other threads:[~2026-05-29 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 14:13 Antoniu Miclaus
2026-05-29 14:13 ` [PATCH v2 1/2] dt-bindings: iio: adc: ad4080: add AD4884 support Antoniu Miclaus
2026-05-29 14:13 ` [PATCH v2 2/2] iio: adc: ad4080: add support for AD4884 Antoniu Miclaus
2026-05-29 17:15 ` 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=20260529181542.7df3bbc5@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=antoniu.miclaus@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@analog.com \
    --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
all inboxes | Powered by JetHome®