mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, bleung@chromium.org, groeck@chromium.org,
	 andriy.shevchenko@linux.intel.com,
	Raag Jadav <raag.jadav@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Convert regulator drivers to use devm_kmemdup_array()
Date: Fri, 28 Feb 2025 21:22:47 +0000	[thread overview]
Message-ID: <174077776750.602863.5336934105237710269.b4-ty@kernel.org> (raw)
In-Reply-To: <20250228072057.151436-1-raag.jadav@intel.com>

On Fri, 28 Feb 2025 12:50:55 +0530, Raag Jadav wrote:
> This series converts regulator drivers to use the newly introduced[1]
> devm_kmemdup_array() helper. This depends on changes available on
> immutable tag[2].
> 
> [1] https://lore.kernel.org/r/20250212062513.2254767-1-raag.jadav@intel.com
> [2] https://lore.kernel.org/r/Z7xGpz3Q4Zj6YHx7@black.fi.intel.com
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: devres: use devm_kmemdup_array()
      commit: 6ddd1159825c516b8f64fda83177c161434141f5
[2/2] regulator: cros-ec: use devm_kmemdup_array()
      commit: c5c4ce6612bb25ce6d6936d8ade96fcba635da54

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:[~2025-02-28 21:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28  7:20 Raag Jadav
2025-02-28  7:20 ` [PATCH v2 1/2] regulator: devres: " Raag Jadav
2025-02-28  7:20 ` [PATCH v2 2/2] regulator: cros-ec: " Raag Jadav
2025-02-28 21:22 ` Mark Brown [this message]
2025-03-06  2:15   ` [PATCH v2 0/2] Convert regulator drivers to " Raag Jadav
2025-03-06  9:19     ` Andy Shevchenko
2025-03-06 10:14       ` Raag Jadav
2025-03-06 11:04         ` Andy Shevchenko
2025-03-06 11:32           ` Raag Jadav
2025-03-06 12:37             ` Andy Shevchenko
2025-03-06 12:50               ` Andy Shevchenko
2025-03-06 13:22           ` Mark Brown

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=174077776750.602863.5336934105237710269.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bleung@chromium.org \
    --cc=groeck@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raag.jadav@intel.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

all inboxes | Powered by JetHome®