linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Vincent Whitchurch <vincent.whitchurch@axis.com>, lgirdwood@gmail.com
Cc: linux-kernel@vger.kernel.org, kernel@axis.com,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Devicetree support for regulator-virtual-consumer
Date: Wed, 02 Mar 2022 17:01:08 +0000	[thread overview]
Message-ID: <164624046835.1145355.163432630010750075.b4-ty@kernel.org> (raw)
In-Reply-To: <20220301111831.3742383-1-vincent.whitchurch@axis.com>

On Tue, 1 Mar 2022 12:18:28 +0100, Vincent Whitchurch wrote:
> This series adds devicetree support for drivers/regulator/virtual.c which is
> useful for development and testing of regulator drivers.
> 
> v2:
> - Only use the "default" supply name if dt
> - Add a comment explaining the "default" supply name
> - Add patch which warns against production use of this driver
> - Add patch to use dev_err_probe
> 
> [...]

Applied to

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

Thanks!

[1/3] regulator: virtual: use dev_err_probe()
      commit: 75c3543e39f0c94644eac5965b3efe50c2c5c39d
[2/3] regulator: virtual: warn against production use
      commit: d2fb5487ecb2a28b61ff261ae18488afc98d24a6
[3/3] regulator: virtual: add devicetree support
      commit: 80c056656d46ffbece6125dee3f25adbc36d1486

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:[~2022-03-02 17:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 11:18 [PATCH v2 0/3] Devicetree support for regulator-virtual-consumer Vincent Whitchurch
2022-03-01 11:18 ` [PATCH v2 1/3] regulator: virtual: use dev_err_probe() Vincent Whitchurch
2022-03-01 11:18 ` [PATCH v2 2/3] regulator: virtual: warn against production use Vincent Whitchurch
2022-03-01 11:18 ` [PATCH v2 3/3] regulator: virtual: add devicetree support Vincent Whitchurch
2022-03-02 17:01 ` 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=164624046835.1145355.163432630010750075.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@axis.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vincent.whitchurch@axis.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).