Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Raag Jadav <raag.jadav@intel.com>
To: perex@perex.cz, tiwai@suse.com, broonie@kernel.org,
	lgirdwood@gmail.com, andriy.shevchenko@linux.intel.com,
	cezary.rojewski@intel.com, amadeuszx.slawinski@linux.intel.com,
	shenghao-ding@ti.com, kevin-lu@ti.com, baojun.xu@ti.com,
	jbrunet@baylibre.com, neil.armstrong@linaro.org,
	khilman@baylibre.com, hayashi.kunihiko@socionext.com,
	mhiramat@kernel.org
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	Raag Jadav <raag.jadav@intel.com>
Subject: [PATCH v2 0/6] Convert sound drivers to use devm_kmemdup_array()
Date: Fri, 28 Feb 2025 11:58:06 +0530	[thread overview]
Message-ID: <20250228062812.150004-1-raag.jadav@intel.com> (raw)

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

v2: Split patch series per subsystem

Raag Jadav (6):
  ASoC: Intel: avs: use devm_kmemdup_array()
  ASoC: hdac_hdmi: use devm_kmemdup_array()
  ASoC: tlv320dac33: use devm_kmemdup_array()
  ASoC: uda1380: use devm_kmemdup_array()
  ASoC: meson: axg-tdm-interface: use devm_kmemdup_array()
  ASoC: uniphier: use devm_kmemdup_array()

 sound/soc/codecs/hdac_hdmi.c         | 3 +--
 sound/soc/codecs/tlv320dac33.c       | 6 ++----
 sound/soc/codecs/uda1380.c           | 6 ++----
 sound/soc/intel/avs/boards/da7219.c  | 3 ++-
 sound/soc/intel/avs/boards/es8336.c  | 3 ++-
 sound/soc/intel/avs/boards/nau8825.c | 3 ++-
 sound/soc/intel/avs/boards/rt274.c   | 3 ++-
 sound/soc/intel/avs/boards/rt286.c   | 3 ++-
 sound/soc/intel/avs/boards/rt298.c   | 3 ++-
 sound/soc/intel/avs/boards/rt5663.c  | 3 ++-
 sound/soc/intel/avs/boards/rt5682.c  | 3 ++-
 sound/soc/meson/axg-tdm-interface.c  | 9 ++-------
 sound/soc/uniphier/aio-cpu.c         | 8 ++------
 13 files changed, 25 insertions(+), 31 deletions(-)


base-commit: b8c38ccb2ca52b9a38cfeb9f89abab5d6e713221
-- 
2.34.1


             reply	other threads:[~2025-02-28  6:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28  6:28 Raag Jadav [this message]
2025-02-28  6:28 ` [PATCH v2 1/6] ASoC: Intel: avs: use devm_kmemdup_array() Raag Jadav
2025-02-28  6:28 ` [PATCH v2 2/6] ASoC: hdac_hdmi: " Raag Jadav
2025-02-28  6:28 ` [PATCH v2 3/6] ASoC: tlv320dac33: " Raag Jadav
2025-02-28  6:28 ` [PATCH v2 4/6] ASoC: uda1380: " Raag Jadav
2025-02-28  6:28 ` [PATCH v2 5/6] ASoC: meson: axg-tdm-interface: " Raag Jadav
2025-02-28  6:28 ` [PATCH v2 6/6] ASoC: uniphier: " Raag Jadav
2025-02-28 21:22 ` [PATCH v2 0/6] Convert sound drivers to " 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=20250228062812.150004-1-raag.jadav@intel.com \
    --to=raag.jadav@intel.com \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=baojun.xu@ti.com \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=hayashi.kunihiko@socionext.com \
    --cc=jbrunet@baylibre.com \
    --cc=kevin-lu@ti.com \
    --cc=khilman@baylibre.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=perex@perex.cz \
    --cc=shenghao-ding@ti.com \
    --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