Devicetree
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, robh@kernel.org, krzk+dt@kernel.org,
	 conor+dt@kernel.org, andreas@kemnade.info,
	Robby Cai <robby.cai@nxp.com>
Cc: 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: Tue, 17 Mar 2026 18:08:18 +0000	[thread overview]
Message-ID: <177377089890.409229.768616051787626910.b4-ty@b4> (raw)
In-Reply-To: <20260313133102.2749890-1-robby.cai@nxp.com>

On Fri, 13 Mar 2026 21:31:00 +0800, Robby Cai wrote:
> regulator: fp9931: Make vin-supply mandatory
> 
> 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.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-7.1

Thanks!

[1/2] dt-bindings: regulator: fp9931: Make vin-supply property as required
      https://git.kernel.org/broonie/regulator/c/d342f5e355aa
[2/2] regulator: fp9931: Fix handling of mandatory "vin" supply
      https://git.kernel.org/broonie/regulator/c/58068932402c

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark


  parent reply	other threads:[~2026-03-17 19:01 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
2026-03-16 18:56       ` Mark Brown
2026-03-17 18:08 ` Mark Brown [this message]
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=177377089890.409229.768616051787626910.b4-ty@b4 \
    --to=broonie@kernel.org \
    --cc=andreas@kemnade.info \
    --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=robby.cai@nxp.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