Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Thu, 02 Jul 2020 16:47:02 +0100
From:   Mark Brown <broonie@kernel.org>
To:     linux-mediatek@lists.infradead.org,
        Anand K Mistry <amistry@google.com>
Cc:     Matthias Brugger <matthias.bgg@gmail.com>,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
        Liam Girdwood <lgirdwood@gmail.com>,
        Rob Herring <robh+dt@kernel.org>,
        Support Opensource <support.opensource@diasemi.com>,
        drinkcat@chromium.org, hsinyi@chromium.org,
        devicetree@vger.kernel.org
In-Reply-To: <20200702031525.2662441-1-amistry@google.com>
References: <20200702031525.2662441-1-amistry@google.com>
Subject: Re: [PATCH 0/4] regulator: da9211: support changing modes
Message-Id: <159370481231.5599.4888173320266148214.b4-ty@kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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