public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Andy Shevchenko" <andy@kernel.org>,
	devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org, "Nuno Sá" <nuno.sa@analog.com>,
	kernel@pengutronix.de, "David Jander" <david@protonic.nl>,
	"David Lechner" <dlechner@baylibre.com>
Subject: Re: [PATCH v6 00/12] iio: dac: ds4424: add DS4402/DS4404 support and scale
Date: Sun, 22 Mar 2026 18:22:45 +0100	[thread overview]
Message-ID: <acAlZe8Y5Qj5a_Vf@pengutronix.de> (raw)
In-Reply-To: <20260322124539.64485997@jic23-huawei>

On Sun, Mar 22, 2026 at 12:45:39PM +0000, Jonathan Cameron wrote:
> On Thu, 26 Feb 2026 10:08:33 +0000
> Jonathan Cameron <jic23@kernel.org> wrote:
> 
> > On Thu, 26 Feb 2026 09:42:20 +0100
> > Oleksij Rempel <o.rempel@pengutronix.de> wrote:
> > 
> > > Hi Jonathan,
> > > 
> > > Should I resend this patch series?  
> > No need.   For future reference I use patchwork.kernel.org to track
> > status of series.   This one is sat there because I need to do a pull
> > request for the precursor fix (which I'll do shortly).  That then needs
> > to loop around into a suitable upstream tree before I can pick this
> > series up on top of it.
> > 
> I merge 7.0-rc4 into the testing branch of iio.git and applied this on top.
> If the build bots are happy I'll push that out as togreg in the next few days.
> A little bit of fuzz in a few patches but otherwise it went on pretty cleanly.
> 
> Please take a quick look to make sure I didn't mess anything up.

LGTM. Thank you!

Best Regards,
Oleksij
-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

      reply	other threads:[~2026-03-22 17:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 13:50 [PATCH v6 00/12] iio: dac: ds4424: add DS4402/DS4404 support and scale Oleksij Rempel
2026-02-10 13:50 ` [PATCH v6 01/12] iio: dac: ds4424: refactor raw access to use bitwise operations Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 02/12] iio: dac: ds4424: ratelimit read errors and use device context Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 03/12] iio: dac: ds4424: sort headers alphabetically Oleksij Rempel
2026-03-22 12:43   ` Jonathan Cameron
2026-02-10 13:51 ` [PATCH v6 04/12] iio: dac: ds4424: rename iio_info struct to avoid ambiguity Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 05/12] iio: dac: ds4424: use device match data for chip info Oleksij Rempel
2026-02-10 14:50   ` Andy Shevchenko
2026-02-10 13:51 ` [PATCH v6 06/12] iio: dac: ds4424: use fsleep() instead of usleep_range() Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 07/12] dt-bindings: iio: dac: maxim,ds4424: add ds4402/ds4404 Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 08/12] iio: dac: ds4424: add DS4402/DS4404 device IDs Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 09/12] iio: dac: ds4424: support per-variant output range limits Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 10/12] iio: dac: ds4424: convert to regmap Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 11/12] dt-bindings: iio: dac: maxim,ds4424: add maxim,rfs-ohms property Oleksij Rempel
2026-02-10 13:51 ` [PATCH v6 12/12] iio: dac: ds4424: add Rfs-based scale and per-variant limits Oleksij Rempel
2026-02-26  8:42 ` [PATCH v6 00/12] iio: dac: ds4424: add DS4402/DS4404 support and scale Oleksij Rempel
2026-02-26 10:08   ` Jonathan Cameron
2026-03-22 12:45     ` Jonathan Cameron
2026-03-22 17:22       ` Oleksij Rempel [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=acAlZe8Y5Qj5a_Vf@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=david@protonic.nl \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --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