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:   Tue, 16 Jun 2020 00:41:19 +0100
From:   Mark Brown <broonie@kernel.org>
To:     Pi-Hsun Shih <pihsun@chromium.org>
Cc:     Benson Leung <bleung@chromium.org>,
        Tzung-Bi Shih <tzungbi@google.com>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@vger.kernel.org>,
        Enric Balletbo i Serra <enric.balletbo@collabora.com>,
        Nicolas Boichat <drinkcat@chromium.org>,
        Yicheng Li <yichengli@chromium.org>,
        Lee Jones <lee.jones@linaro.org>,
        open list <linux-kernel@vger.kernel.org>,
        Guenter Roeck <groeck@chromium.org>
In-Reply-To: <20200612040526.192878-1-pihsun@chromium.org>
References: <20200612040526.192878-1-pihsun@chromium.org>
Subject: Re: [PATCH v6 0/3] Add support for voltage regulator on ChromeOS EC.
Message-Id: <159226447507.27673.12544473672334795721.b4-ty@kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, 12 Jun 2020 12:05:17 +0800, Pi-Hsun Shih wrote:
> Add support for controlling voltage regulator that is connected and
> controlled by ChromeOS EC. Kernel controls these regulators through
> newly added EC host commands.
> 
> Changes from v5:
> * Move new host command to a separate patch.
> * Use devm_regulator_register.
> * Address review comments.
> 
> [...]

Applied to

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

Thanks!

[1/3] dt-bindings: regulator: Add DT binding for cros-ec-regulator
      commit: 54bd53b9c11ed856abeedbf1ce92a19b546f56cf
[2/3] platform/chrome: cros_ec: Add command for regulator control.
      commit: dff08caf35ecef4f7647f8b1e40877a254852a2b
[3/3] regulator: Add driver for cros-ec-regulator
      commit: 8d9f8d57e023893bfa708d83e3a787e77766a378

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