From: Raag Jadav <raag.jadav@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, bleung@chromium.org, groeck@chromium.org,
andriy.shevchenko@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Convert regulator drivers to use devm_kmemdup_array()
Date: Thu, 6 Mar 2025 04:15:55 +0200 [thread overview]
Message-ID: <Z8kFW13EyR0YXnJd@black.fi.intel.com> (raw)
In-Reply-To: <174077776750.602863.5336934105237710269.b4-ty@kernel.org>
On Fri, Feb 28, 2025 at 09:22:47PM +0000, Mark Brown wrote:
> 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
Thank you.
Unless there's a nuance intended in the merge series title that I'm unable
to understand, it probably seems incomplete.
Raag
next prev parent reply other threads:[~2025-03-06 2:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 7:20 [PATCH v2 0/2] Convert regulator drivers to use devm_kmemdup_array() 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 ` [PATCH v2 0/2] Convert regulator drivers to " Mark Brown
2025-03-06 2:15 ` Raag Jadav [this message]
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=Z8kFW13EyR0YXnJd@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bleung@chromium.org \
--cc=broonie@kernel.org \
--cc=groeck@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.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