From: Robby Cai <robby.cai@nxp.com>
To: Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, andreas@kemnade.info,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev
Subject: Re: [PATCH v2 0/2] regulator: fp9931: Make vin-supply mandatory
Date: Mon, 16 Mar 2026 15:31:25 +0800 [thread overview]
Message-ID: <20260316073125.GB3683539@shlinux88> (raw)
In-Reply-To: <d57d9f4d-098a-4663-aa72-4d3104451aae@sirena.org.uk>
On Fri, Mar 13, 2026 at 04:27:21PM +0000, Mark Brown wrote:
> On Fri, Mar 13, 2026 at 01:31:23PM +0000, Mark Brown wrote:
> > On Fri, Mar 13, 2026 at 09:31:00PM +0800, Robby Cai wrote:
> > > The FP9931 regulator requires a valid "vin" supply to operate correctly.
> > > Therefore, the driver should treat "vin" as a mandatory supply.
>
> > > This patchset updates the binding documentation to mark vin-supply as a
> > > required property, and modifies the driver accordingly. As suggested in
> > > the reviews from Andreas and Mark, v2 switches to using
> > > devm_regulator_get() since the supply is mandatory.
>
> > Please do not submit new versions of already applied patches, please
> > submit incremental updates to the existing code. Modifying existing
> > commits creates problems for other users building on top of those
> > commits so it's best practice to only change pubished git commits if
> > absolutely essential.
>
> Your v1 was at the tip of the branch so I did actually just drop it, but
> please don't do this.
Thanks for the clarification.
Just to confirm: since you already dropped the v1 from your tree,
does that mean I should wait and only send an incremental patch
when there is a further change needed?
Regards,
Robby
next prev parent reply other threads:[~2026-03-16 7:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 13:31 [PATCH v2 0/2] regulator: fp9931: Make vin-supply mandatory Robby Cai
2026-03-13 13:31 ` [PATCH v2 1/2] dt-bindings: regulator: fp9931: Make vin-supply property as required Robby Cai
2026-03-13 13:33 ` Mark Brown
2026-03-13 14:16 ` Andreas Kemnade
2026-03-13 14:38 ` Mark Brown
2026-03-13 17:24 ` Conor Dooley
2026-03-13 13:31 ` [PATCH v2 2/2] regulator: fp9931: Fix handling of mandatory "vin" supply Robby Cai
2026-03-13 17:24 ` Conor Dooley
2026-03-16 7:26 ` Robby Cai
2026-03-16 14:28 ` Andreas Kemnade
2026-03-13 13:31 ` [PATCH v2 0/2] regulator: fp9931: Make vin-supply mandatory Mark Brown
2026-03-13 16:27 ` Mark Brown
2026-03-16 7:31 ` Robby Cai [this message]
2026-03-16 18:56 ` Mark Brown
2026-03-17 18:08 ` Mark Brown
2026-03-17 19:00 ` 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=20260316073125.GB3683539@shlinux88 \
--to=robby.cai@nxp.com \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.