From: Mark Brown <broonie@kernel.org>
To: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Woodrow Douglass <wdouglass@carnegierobotics.com>,
linux-kernel@vger.kernel.org,
Michael Hennerich <michael.hennerich@analog.com>,
Support Opensource <support.opensource@diasemi.com>,
Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Saravanan Sekar <sravanhome@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Jagan Teki <jagan@amarulasolutions.com>,
Icenowy Zheng <icenowy@aosc.io>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v3 0/2] regulator: Rework i2c_device_id initialisation
Date: Mon, 29 Jun 2026 19:10:45 +0100 [thread overview]
Message-ID: <d1e9fb06-893e-44dd-8231-ecddbbfe242e@sirena.org.uk> (raw)
In-Reply-To: <cover.1781888370.git.u.kleine-koenig@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
On Fri, Jun 19, 2026 at 07:17:07PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> Hello,
>
> v2 is available at https://lore.kernel.org/lkml/cover.1779184320.git.u.kleine-koenig@baylibre.com .
>
> The only change is that I rebased to next-20260619 and dropped the
> adaptions to the of_regulator_match arrays that Laurent pointed out to
> not belong into this patch set.
This needs rebasing against current code.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-06-29 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 17:17 [PATCH v3 0/2] regulator: Rework i2c_device_id initialisation Uwe Kleine-König (The Capable Hub)
2026-06-19 17:17 ` [PATCH v3 2/2] regulator: Use named initializers for arrays of i2c_device_data Uwe Kleine-König (The Capable Hub)
2026-06-29 18:10 ` Mark Brown [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=d1e9fb06-893e-44dd-8231-ecddbbfe242e@sirena.org.uk \
--to=broonie@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=icenowy@aosc.io \
--cc=ivo.ivanov.ivanov1@gmail.com \
--cc=jagan@amarulasolutions.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=michael.hennerich@analog.com \
--cc=sravanhome@gmail.com \
--cc=support.opensource@diasemi.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=wdouglass@carnegierobotics.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