mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
	 Jerome Brunet <jbrunet@baylibre.com>
Cc: linux-kernel@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH v2 0/3] regulator: init_data handling update
Date: Wed, 23 Oct 2024 00:04:04 +0100	[thread overview]
Message-ID: <172963824495.326511.4469889963370006870.b4-ty@kernel.org> (raw)
In-Reply-To: <20241008-regulator-ignored-data-v2-0-d1251e0ee507@baylibre.com>

On Tue, 08 Oct 2024 18:07:00 +0200, Jerome Brunet wrote:
> This patchset groups the regulator patches around the init_data topic
> discussed on pmbus write protect patchset [1]
> 
> [1]: https://lore.kernel.org/r/20240920-pmbus-wp-v1-0-d679ef31c483@baylibre.com
> 
> 

Applied to

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

Thanks!

[1/3] regulator: core: do not silently ignore provided init_data
      commit: cd7a38c40b231350a3cd0fd774f4e6bb68c4b411
[2/3] regulator: core: add callback to perform runtime init
      commit: cfcdf395c21eeac4543d2b8fef9d29ae9e4559e9
[3/3] regulator: core: remove machine init callback from config
      commit: 602ff58ae4fe4289b0ca71cba9fb82f7de92cd64

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:[~2024-10-22 23:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08 16:07 Jerome Brunet
2024-10-08 16:07 ` [PATCH v2 1/3] regulator: core: do not silently ignore provided init_data Jerome Brunet
2025-02-09 14:16   ` Luca Weiss
2025-02-09 19:05     ` Jerome Brunet
2025-02-10 13:06       ` Mark Brown
2024-10-08 16:07 ` [PATCH v2 2/3] regulator: core: add callback to perform runtime init Jerome Brunet
2024-10-08 16:07 ` [PATCH v2 3/3] regulator: core: remove machine init callback from config Jerome Brunet
2024-10-22 23:04 ` 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=172963824495.326511.4469889963370006870.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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

all inboxes | Powered by JetHome®