From: Raag Jadav <raag.jadav@intel.com>
To: perex@perex.cz, tiwai@suse.com, broonie@kernel.org,
lgirdwood@gmail.com, deller@gmx.de,
andriy.shevchenko@linux.intel.com, sre@kernel.org,
sakari.ailus@linux.intel.com, mchehab@kernel.org,
hverkuil-cisco@xs4all.nl, jdmason@kudzu.us,
fancer.lancer@gmail.com
Cc: linux-sound@vger.kernel.org, linux-fbdev@vger.kernel.org,
linux-pm@vger.kernel.org, linux-media@vger.kernel.org,
ntb@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 00/13] Convert to use devm_kmemdup_array()
Date: Mon, 24 Feb 2025 14:39:07 +0200 [thread overview]
Message-ID: <Z7xoa9FbuvIaTJFt@black.fi.intel.com> (raw)
In-Reply-To: <20250221165333.2780888-1-raag.jadav@intel.com>
On Fri, Feb 21, 2025 at 10:23:20PM +0530, Raag Jadav wrote:
> This series is the second wave of patches to add users of newly introduced
> devm_kmemdup_array() helper. Original series on [1].
>
> This depends on changes available on immutable tag[2]. Feel free to pick
> your subsystem patches with it, or share your preferred way to route them.
>
> [1] https://lore.kernel.org/r/20250212062513.2254767-1-raag.jadav@intel.com
> [2] https://lore.kernel.org/r/Z7cqCaME4LxTTBn6@black.fi.intel.com
Update: Anyone wishing to pull from this series, please use the updated
tag[3]. I'll wait for a few days for review comments and send out a v2
with fbdev fix.
[3] https://lore.kernel.org/r/Z7xGpz3Q4Zj6YHx7@black.fi.intel.com
Apologies for the inconvenience.
Raag
next prev parent reply other threads:[~2025-02-24 12:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 16:53 [PATCH v1 00/13] Convert to use devm_kmemdup_array() Raag Jadav
2025-02-21 16:53 ` [PATCH v1 01/13] ASoC: Intel: avs: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 02/13] ASoC: hdac_hdmi: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 03/13] ASoC: tlv320dac33: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 04/13] ASoC: uda1380: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 05/13] ASoC: meson: axg-tdm-interface: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 06/13] ASoC: uniphier: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 07/13] fbdev: pxafb: " Raag Jadav
2025-02-21 21:41 ` kernel test robot
2025-02-24 10:58 ` Andy Shevchenko
2025-02-24 11:24 ` Raag Jadav
2025-02-24 11:41 ` Andy Shevchenko
2025-02-24 12:22 ` Raag Jadav
2025-02-24 12:28 ` Andy Shevchenko
2025-02-21 16:53 ` [PATCH v1 08/13] power: supply: sc27xx: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 09/13] regulator: devres: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 10/13] regulator: cros-ec: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 11/13] media: atmel-isi: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 12/13] media: stm32-dcmi: " Raag Jadav
2025-02-21 16:53 ` [PATCH v1 13/13] ntb: idt: " Raag Jadav
2025-02-21 17:05 ` Dave Jiang
2025-02-22 9:27 ` Raag Jadav
2025-02-21 22:51 ` (subset) [PATCH v1 00/13] Convert to " Sebastian Reichel
2025-02-24 12:39 ` Raag Jadav [this message]
2025-02-24 13:46 ` Mark Brown
2025-02-24 14:29 ` Raag Jadav
2025-02-28 21:22 ` (subset) " 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=Z7xoa9FbuvIaTJFt@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=deller@gmx.de \
--cc=fancer.lancer@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jdmason@kudzu.us \
--cc=lgirdwood@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ntb@lists.linux.dev \
--cc=perex@perex.cz \
--cc=sakari.ailus@linux.intel.com \
--cc=sre@kernel.org \
--cc=tiwai@suse.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).