From: Lee Jones <lee@kernel.org>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alistair Francis <alistair@alistair23.me>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Frank Li <Frank.li@nxp.com>,
Andreas Kemnade <akemnade@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: (subset) [PATCH v3 1/3] dt-bindings: mfd: sy7636a: Add missing gpio pins and supply
Date: Tue, 21 Oct 2025 11:46:15 +0100 [thread overview]
Message-ID: <20251021104615.GC475031@google.com> (raw)
In-Reply-To: <20251020151511.1fd8611b@kemnade.info>
On Mon, 20 Oct 2025, Andreas Kemnade wrote:
> On Wed, 08 Oct 2025 16:31:57 +0100
> Lee Jones <lee@kernel.org> wrote:
>
> > On Wed, 17 Sep 2025 09:14:29 +0200, Andreas Kemnade wrote:
> > > To be able to fully describe how the SY7636A is connected to the system,
> > > add properties for the EN and VCOM_EN pins. To squeeze out every bit
> > > of unused current, in many devices it is possible to power off the
> > > complete chip. Add an input regulator to allow that.
> > >
> > >
> >
> > Applied, thanks!
> >
> > [1/3] dt-bindings: mfd: sy7636a: Add missing gpio pins and supply
> > commit: 7d983e997cb53d4c48b61b105163c31c92a35823
> >
> hmm, what is the fate of this? I remember having seen this in your
> for-mfd-next-next branch. But now I cannot find it neither in
> your mfd-next nor your mfd-next-next nor general linux-next.
It's still applied, only with a different subject line:
https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git/commit/?h=for-mfd-next&id=cb62b0ea2c88c8a3d38b7b4991adbc0aacdb1418
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-10-21 10:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 7:14 [PATCH v3 0/3] regulator: sy7636a: define and init all resources needed Andreas Kemnade
2025-09-17 7:14 ` [PATCH v3 1/3] dt-bindings: mfd: sy7636a: Add missing gpio pins and supply Andreas Kemnade
2025-10-08 15:31 ` (subset) " Lee Jones
2025-10-20 13:15 ` Andreas Kemnade
2025-10-21 10:46 ` Lee Jones [this message]
2025-09-17 7:14 ` [PATCH v3 2/3] regulator: sy7636a: add gpios and input regulator Andreas Kemnade
2025-09-17 7:14 ` [PATCH v3 3/3] ARM: dts: imx: e70k02: add sy7636 Andreas Kemnade
2025-10-20 12:48 ` Shawn Guo
2025-10-17 11:24 ` (subset) [PATCH v3 0/3] regulator: sy7636a: define and init all resources needed Mark Brown
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=20251021104615.GC475031@google.com \
--to=lee@kernel.org \
--cc=Frank.li@nxp.com \
--cc=akemnade@kernel.org \
--cc=alistair@alistair23.me \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).