linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH v6 0/3] Add support for voltage regulator on ChromeOS EC.
Date: Tue, 16 Jun 2020 00:41:19 +0100	[thread overview]
Message-ID: <159226447507.27673.12544473672334795721.b4-ty@kernel.org> (raw)
In-Reply-To: <20200612040526.192878-1-pihsun@chromium.org>

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

      parent reply	other threads:[~2020-06-15 23:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12  4:05 [PATCH v6 0/3] Add support for voltage regulator on ChromeOS EC Pi-Hsun Shih
2020-06-12  4:05 ` [PATCH v6 1/3] dt-bindings: regulator: Add DT binding for cros-ec-regulator Pi-Hsun Shih
2020-06-12  4:05 ` [PATCH v6 2/3] platform/chrome: cros_ec: Add command for regulator control Pi-Hsun Shih
2020-06-12  4:05 ` [PATCH v6 3/3] regulator: Add driver for cros-ec-regulator Pi-Hsun Shih
2020-06-15 23:41 ` 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=159226447507.27673.12544473672334795721.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=bleung@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=drinkcat@chromium.org \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@chromium.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pihsun@chromium.org \
    --cc=tzungbi@google.com \
    --cc=yichengli@chromium.org \
    /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).