public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: linux-iio@vger.kernel.org, "Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Michael Hennerich" <michael.hennerich@analog.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Mark Brown" <broonie@kernel.org>,
	linux-kernel@vger.kernel.org,
	"Stefan Popa" <stefan.popa@analog.com>,
	devicetree@vger.kernel.org,
	"Julien Stephan" <jstephan@baylibre.com>
Subject: Re: [PATCH v4 2/2] iio: adc: ad7380: new driver for AD7380 ADCs
Date: Sat, 17 Feb 2024 16:20:14 +0000	[thread overview]
Message-ID: <20240217162014.17033d64@jic23-huawei> (raw)
In-Reply-To: <CAMknhBGg0hHXrd3K92tgHHTnfbk7dLAMvtTSZff1P-C3=9nFaw@mail.gmail.com>

On Fri, 16 Feb 2024 14:34:01 -0600
David Lechner <dlechner@baylibre.com> wrote:

> On Wed, Jan 10, 2024 at 2:29 PM David Lechner <dlechner@baylibre.com> wrote:
> >
> > This adds a new driver for the AD7380 family ADCs.
> >
> > The driver currently implements basic support for the AD7380, AD7381,
> > AD7383, and AD7384 2-channel differential ADCs. Support for additional
> > single-ended and 4-channel chips that use the same register map as well
> > as additional features of the chip will be added in future patches.
> >  
> 
> Hi Jonathan,
> 
> We have some additional features to add to this driver we are working
> on that look like they might affect userspace. Can we hold off on
> sending this one to Greg for 6.9? That way we will have more time to
> sort that out without having to worry about breaking userspace.

Ok. Hopefully rebasing my tree won't cause others too many downstream
problems. Generally I only do this if there is an invalid tag or similar
that must be fixed.  There is normally a window of a weekish
between me picking it up and pushing out for linux-next to pick up and
hopefully issues like this get spotted in that window.
Ah well, sometimes things don't work out how we would like them to.

Dropped the 3 patches (original driver and a fix) from the togreg branch.

Jonathan

  reply	other threads:[~2024-02-17 16:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 20:28 [PATCH v4 0/2] iio: adc: add new ad7380 driver David Lechner
2024-01-10 20:28 ` [PATCH v4 1/2] dt-bindings: iio: adc: Add binding for AD7380 ADCs David Lechner
2024-01-11 16:38   ` Conor Dooley
2024-01-10 20:28 ` [PATCH v4 2/2] iio: adc: ad7380: new driver " David Lechner
2024-02-16 20:34   ` David Lechner
2024-02-17 16:20     ` Jonathan Cameron [this message]
2024-02-18 21:57       ` David Lechner
2024-02-19 19:47   ` David Lechner
2024-02-24 11:06     ` Jonathan Cameron
2024-01-13 16:14 ` [PATCH v4 0/2] iio: adc: add new ad7380 driver 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=20240217162014.17033d64@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jstephan@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=michael.hennerich@analog.com \
    --cc=nuno.sa@analog.com \
    --cc=robh+dt@kernel.org \
    --cc=stefan.popa@analog.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