From: zhong jiang <zhongjiang@huawei.com>
To: <tiwai@suse.com>, <perex@perex.cz>, <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <bgoswami@codeaurora.org>,
<plai@codeaurora.org>, <alsa-devel@alsa-project.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] sound: Use kmemdup to replace kzalloc + memcpy
Date: Sat, 8 Sep 2018 16:36:18 +0800 [thread overview]
Message-ID: <1536395780-18725-1-git-send-email-zhongjiang@huawei.com> (raw)
I find the issue with the help of Coccinelle.
zhong jiang (2):
sound: q6core: Use kmemdup to replace kzalloc + memcpy
sound: skl-topology: Use kmemdup to replace kzalloc + memcpy
sound/soc/intel/skylake/skl-topology.c | 3 +--
sound/soc/qcom/qdsp6/q6core.c | 8 ++------
2 files changed, 3 insertions(+), 8 deletions(-)
--
1.7.12.4
next reply other threads:[~2018-09-08 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-08 8:36 zhong jiang [this message]
2018-09-08 8:36 ` [PATCH 1/2] sound: q6core: Use kmemdup to replace kzalloc + memcpy zhong jiang
2018-09-10 14:19 ` Mark Brown
2018-09-11 1:13 ` zhong jiang
2018-09-08 8:36 ` [PATCH 2/2] sound: skl-topology: " zhong jiang
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=1536395780-18725-1-git-send-email-zhongjiang@huawei.com \
--to=zhongjiang@huawei.com \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=plai@codeaurora.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).