From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robh+dt@kernel.org>,
Adam Ward <Adam.Ward.opensource@diasemi.com>
Cc: devicetree@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Support Opensource <support.opensource@diasemi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 0/4] regulator: da9121: add DA914x support
Date: Wed, 01 Dec 2021 18:32:31 +0000 [thread overview]
Message-ID: <163838355167.2179928.18428295245396475167.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1638223185.git.Adam.Ward.opensource@diasemi.com>
On Mon, 29 Nov 2021 22:10:09 +0000, Adam Ward wrote:
> This series extends the DA9121 driver to add support for related products:
>
> DA9141, 40A, Quad-Phase
> DA9142, 20A, Dual-Phase
>
> The changing of current limit when active is now prohibited, for the range,
> due to possibility of undefined behaviour during transition
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/4] dt-bindings: da9121: Remove erroneous compatible from binding
commit: b9c044b7d63b2ffae9664349721c80c4ab3e56c9
[2/4] dt-bindings: da9121: Add DA914x binding info
commit: d07fef2fcd4d79198a700f4b4d2ca4670649c9ff
[3/4] regulator: da9121: Prevent current limit change when enabled
commit: 24f0853228f3b98f1ef08d5824376c69bb8124d2
[4/4] regulator: da9121: Add DA914x support
commit: c5187a245e9bb0af2da8d37ede191569c824c66b
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
prev parent reply other threads:[~2021-12-01 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 22:10 [PATCH V4 0/4] regulator: da9121: add DA914x support Adam Ward
2021-11-29 22:10 ` [PATCH V4 1/4] dt-bindings: da9121: Remove erroneous compatible from binding Adam Ward
2021-11-29 22:10 ` [PATCH V4 2/4] dt-bindings: da9121: Add DA914x binding info Adam Ward
2021-11-29 22:10 ` [PATCH V4 3/4] regulator: da9121: Prevent current limit change when enabled Adam Ward
2021-11-29 22:10 ` [PATCH V4 4/4] regulator: da9121: Add DA914x support Adam Ward
2021-12-01 18:32 ` 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=163838355167.2179928.18428295245396475167.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=Adam.Ward.opensource@diasemi.com \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=support.opensource@diasemi.com \
/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.