From: Mark Brown <broonie@kernel.org>
To: linux-mediatek@lists.infradead.org, Anand K Mistry <amistry@google.com>
Cc: devicetree@vger.kernel.org, drinkcat@chromium.org,
Support Opensource <support.opensource@diasemi.com>,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
hsinyi@chromium.org, Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] regulator: da9211: support changing modes
Date: Thu, 02 Jul 2020 16:47:02 +0100 [thread overview]
Message-ID: <159370481231.5599.4888173320266148214.b4-ty@kernel.org> (raw)
In-Reply-To: <20200702031525.2662441-1-amistry@google.com>
On Thu, 2 Jul 2020 13:15:21 +1000, Anand K Mistry wrote:
> This patchset adds support for being able to change regulator modes for
> the da9211 regulator. This is needed to allow the voltage scaling
> support in the MT8173 SoC to be used in the elm (Acer Chromebook R13)
> and hana (several Lenovo Chromebooks) devices.
>
>
> Anand K Mistry (4):
> regulator: da9211: Move buck modes into header file
> dt-bindings: regulator: da9211: Document allowed modes
> regulator: da9211: Implement of_map_mode
> arm64: dts: mediatek: Update allowed regulator modes for elm boards
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/3] regulator: da9211: Move buck modes into header file
commit: 6c8b65950b1c75b9e41b5bf314f5d7b81df91272
[2/3] regulator: da9211: Document allowed modes
commit: 650e5adae0197bb9ecaa48b98b8ada1cc6772fb0
[3/3] regulator: da9211: Implement of_map_mode
commit: 6f1f1a8039e5f7a61e932d6a9a50708c56e21033
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
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
prev parent reply other threads:[~2020-07-02 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 3:15 [PATCH 0/4] regulator: da9211: support changing modes Anand K Mistry
2020-07-02 3:15 ` [PATCH 1/4] regulator: da9211: Move buck modes into header file Anand K Mistry
2020-07-02 3:15 ` [PATCH 2/4] dt-bindings: regulator: da9211: Document allowed modes Anand K Mistry
2020-07-02 3:15 ` [PATCH 3/4] regulator: da9211: Implement of_map_mode Anand K Mistry
2020-07-02 3:15 ` [PATCH 4/4] arm64: dts: mediatek: Update allowed regulator modes for elm boards Anand K Mistry
2020-07-02 15:47 ` 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=159370481231.5599.4888173320266148214.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=amistry@google.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=hsinyi@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).