From: Li Zetao <lizetao1@huawei.com>
To: <lgirdwood@gmail.com>, <broonie@kernel.org>, <perex@perex.cz>,
<tiwai@suse.com>, <pierre-louis.bossart@linux.intel.com>,
<peter.ujfalusi@linux.intel.com>,
<yung-chuan.liao@linux.intel.com>,
<ranjani.sridharan@linux.intel.com>, <daniel.baluta@nxp.com>,
<kai.vehmanen@linux.intel.com>, <daniel.beer@igorinstitute.com>,
<Jonathan.Cameron@huawei.com>, <luca.ceresoli@bootlin.com>,
<luzmaximilian@gmail.com>, <u.kleine-koenig@pengutronix.de>
Cc: <lizetao1@huawei.com>, <alsa-devel@alsa-project.org>,
<sound-open-firmware@alsa-project.org>
Subject: [PATCH -next 0/2] Use devm_kmemdup to replace devm_kmalloc + memcpy
Date: Thu, 10 Aug 2023 19:47:36 +0800 [thread overview]
Message-ID: <20230810114738.2103792-1-lizetao1@huawei.com> (raw)
This patch set use the helper function devm_kmemdup() to replace
devm_kmalloc + memcpy, which is the same as implementing the function
separately.
Li Zetao (2):
ASoC: tas5805m: Use devm_kmemdup to replace devm_kmalloc + memcpy
ASoC: SOF: ipc3: Use devm_kmemdup to replace devm_kmalloc + memcpy
sound/soc/codecs/tas5805m.c | 3 +--
sound/soc/sof/ipc3.c | 5 +----
2 files changed, 2 insertions(+), 6 deletions(-)
--
2.34.1
next reply other threads:[~2023-08-10 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 11:47 Li Zetao [this message]
2023-08-10 11:47 ` [PATCH -next 1/2] ASoC: tas5805m: Use devm_kmemdup to replace devm_kmalloc + memcpy Li Zetao
2023-08-10 18:55 ` Daniel Beer
2023-08-10 11:47 ` [PATCH -next 2/2] ASoC: SOF: ipc3: " Li Zetao
2023-08-11 15:32 ` Luca Ceresoli
2023-08-15 19:17 ` [PATCH -next 0/2] " 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=20230810114738.2103792-1-lizetao1@huawei.com \
--to=lizetao1@huawei.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=daniel.beer@igorinstitute.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=luca.ceresoli@bootlin.com \
--cc=luzmaximilian@gmail.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=yung-chuan.liao@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.