mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 Linus Walleij <linus.walleij@linaro.org>,
	 Liam Girdwood <lgirdwood@gmail.com>,
	Julien Panis <jpanis@baylibre.com>,
	 Michael Walle <mwalle@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-gpio@vger.kernel.org
Subject: Re: (subset) [PATCH v3 0/8] mfd: tps6594: Add TI TPS652G1 support
Date: Thu, 10 Jul 2025 16:12:48 +0100	[thread overview]
Message-ID: <175216036871.755014.4346115067078586712.b4-ty@kernel.org> (raw)
In-Reply-To: <20250703113153.2447110-1-mwalle@kernel.org>

On Thu, 03 Jul 2025 13:31:45 +0200, Michael Walle wrote:
> Add support for the TI TPS652G1 PMIC which is a stripped down
> version of the TPS65224. Support for the latter has already been
> merged. Refactor the regulator driver to ease adding new devices.
> After doing that adding the TPS652G1 variant is really straight
> forward. Some care has to be taken by the interrupt handling (of the
> regulator part) because there interrupts are used for voltage
> monitoring which this variant doesn't have.
> 
> [...]

Applied to

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

Thanks!

[5/8] regulator: tps6594-regulator: remove interrupt_count
      commit: 16d1a9bf36ef649b1fdb866985b4b87584491fac
[6/8] regulator: tps6594-regulator: remove hardcoded buck config
      commit: 180a135eafa9e05657559bb04cc9eb6a86ca45f3
[7/8] regulator: tps6594-regulator: refactor variant descriptions
      commit: e64ee27abfe1e9baea14b31c0a6b6bf93ac8652c
[8/8] regulator: tps6594-regulator: Add TI TPS652G1 PMIC regulators
      commit: b30d390812c8559c5835f8ae5f490b38488fafc8

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:[~2025-07-10 15:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03 11:31 Michael Walle
2025-07-03 11:31 ` [PATCH v3 1/8] dt-bindings: mfd: ti,tps6594: Add TI TPS652G1 PMIC Michael Walle
2025-07-03 11:31 ` [PATCH v3 2/8] mfd: tps6594: Add TI TPS652G1 support Michael Walle
2025-07-03 11:31 ` [PATCH v3 3/8] misc: tps6594-pfsm: Add TI TPS652G1 PMIC PFSM Michael Walle
2025-07-03 11:31 ` [PATCH v3 4/8] pinctrl: pinctrl-tps6594: Add TPS652G1 PMIC pinctrl and GPIO Michael Walle
2025-07-03 11:31 ` [PATCH v3 5/8] regulator: tps6594-regulator: remove interrupt_count Michael Walle
2025-07-03 11:31 ` [PATCH v3 6/8] regulator: tps6594-regulator: remove hardcoded buck config Michael Walle
2025-07-03 11:31 ` [PATCH v3 7/8] regulator: tps6594-regulator: refactor variant descriptions Michael Walle
2025-07-03 11:31 ` [PATCH v3 8/8] regulator: tps6594-regulator: Add TI TPS652G1 PMIC regulators Michael Walle
2025-07-10  9:39 ` [PATCH v3 0/8] mfd: tps6594: Add TI TPS652G1 support Lee Jones
2025-07-10 15:12 ` 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=175216036871.755014.4346115067078586712.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=arnd@arndb.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jpanis@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mwalle@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®