[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174077775241.602624.10081824574862077124.b4-ty@kernel.org>
Date: Fri, 28 Feb 2025 21:22:32 +0000
From: Mark Brown <broonie@...nel.org>
To: perex@...ex.cz, tiwai@...e.com, lgirdwood@...il.com,
andriy.shevchenko@...ux.intel.com, cezary.rojewski@...el.com,
amadeuszx.slawinski@...ux.intel.com, shenghao-ding@...com, kevin-lu@...com,
baojun.xu@...com, jbrunet@...libre.com, neil.armstrong@...aro.org,
khilman@...libre.com, hayashi.kunihiko@...ionext.com, mhiramat@...nel.org,
Raag Jadav <raag.jadav@...el.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/6] Convert sound drivers to use
devm_kmemdup_array()
On Fri, 28 Feb 2025 11:58:06 +0530, Raag Jadav wrote:
> This series converts sound 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/sound.git for-next
Thanks!
[1/6] ASoC: Intel: avs: use devm_kmemdup_array()
commit: 0bd862846e7f89910252cbef8718a757950f1683
[2/6] ASoC: hdac_hdmi: use devm_kmemdup_array()
commit: 3e706be02befae55b50b240d4360b5993f9879a8
[3/6] ASoC: tlv320dac33: use devm_kmemdup_array()
commit: 69aaab0e65e9bd7601740c1e14cc6de86dafb621
[4/6] ASoC: uda1380: use devm_kmemdup_array()
commit: d9d71a6e2d19a2f3ccebea0092b8ddc1e935886f
[5/6] ASoC: meson: axg-tdm-interface: use devm_kmemdup_array()
commit: b26205e172ca035e327e49edb0c2611e5d2ede8d
[6/6] ASoC: uniphier: use devm_kmemdup_array()
commit: c173b5ee81a25e8aafb21ccdb7ab457da7783bf1
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
Powered by blists - more mailing lists