[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <173644860244.654853.1911781164332852260.b4-ty@kernel.org>
Date: Thu, 09 Jan 2025 18:50:02 +0000
From: Mark Brown <broonie@...nel.org>
To: Oleksij Rempel <o.rempel@...gutronix.de>,
Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>, Donald Hunter <donald.hunter@...il.com>,
Jonathan Corbet <corbet@....net>, Liam Girdwood <lgirdwood@...il.com>,
Kory Maincent <kory.maincent@...tlin.com>
Cc: Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-doc@...r.kernel.org, Kyle Swenson <kyle.swenson@....tech>,
Dent Project <dentproject@...uxfoundation.org>, kernel@...gutronix.de,
Maxime Chevallier <maxime.chevallier@...tlin.com>,
Kalesh AP <kalesh-anakkur.purayil@...adcom.com>,
Andrew Lunn <andrew@...n.ch>
Subject: Re: (subset) [PATCH net-next v2 00/15] Arrange PSE core and update
TPS23881 driver
On Thu, 09 Jan 2025 11:17:54 +0100, Kory Maincent wrote:
> This patch includes several improvements to the PSE core for better
> implementation and maintainability:
>
> - Move the conversion between current limit and power limit from the driver
> to the PSE core.
> - Update power and current limit checks.
> - Split the ethtool_get_status callback into multiple callbacks.
> - Add support for PSE device index.
> - Fix PSE PI of_node detection.
> - Clean ethtool header of PSE structures.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[13/15] regulator: core: Resolve supply using of_node from regulator_config
commit: c3ad22ad34f81a8906dba02ea8cc9756d2ce7b50
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
Powered by blists - more mailing lists