From: Trevor Wu <trevor.wu@mediatek.com>
To: <broonie@kernel.org>, <lgirdwood@gmail.com>, <tiwai@suse.com>,
<perex@perex.cz>, <matthias.bgg@gmail.com>,
<angelogioacchino.delregno@collabora.com>
Cc: <trevor.wu@mediatek.com>, <jiaxin.yu@mediatek.com>,
<alsa-devel@alsa-project.org>,
<linux-mediatek@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH 0/4] ASoC: mediatek: fix coverity problems
Date: Tue, 7 Mar 2023 12:09:34 +0800 [thread overview]
Message-ID: <20230307040938.7484-1-trevor.wu@mediatek.com> (raw)
Coverity reports some UNINIT and CERT STR31-C problems, so we add
initialization and dai id check to resolve problems.
Trevor Wu (4):
ASoC: mediatek: mt8195: add dai id check before accessing array
ASoC: mediatek: mt9195-mt6359: fix UNINIT problem
ASoC: mediatek: mt6358: fix UNINIT problem
ASoC: mediatek: mt6359: fix UNINIT problem
sound/soc/codecs/mt6358.c | 2 +-
sound/soc/codecs/mt6359.c | 2 +-
sound/soc/mediatek/mt8195/mt8195-dai-adda.c | 17 +-
sound/soc/mediatek/mt8195/mt8195-dai-etdm.c | 177 +++++++++++++++++---
sound/soc/mediatek/mt8195/mt8195-dai-pcm.c | 26 ++-
sound/soc/mediatek/mt8195/mt8195-mt6359.c | 2 +-
6 files changed, 188 insertions(+), 38 deletions(-)
--
2.18.0
next reply other threads:[~2023-03-07 4:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 4:09 Trevor Wu [this message]
2023-03-07 4:09 ` [PATCH 1/4] ASoC: mediatek: mt8195: add dai id check before accessing array Trevor Wu
2023-03-07 4:09 ` [PATCH 2/4] ASoC: mediatek: mt9195-mt6359: fix UNINIT problem Trevor Wu
2023-03-07 4:09 ` [PATCH 3/4] ASoC: mediatek: mt6358: " Trevor Wu
2023-03-07 4:09 ` [PATCH 4/4] ASoC: mediatek: mt6359: " Trevor Wu
2023-03-13 19:07 ` [PATCH 0/4] ASoC: mediatek: fix coverity problems 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=20230307040938.7484-1-trevor.wu@mediatek.com \
--to=trevor.wu@mediatek.com \
--cc=alsa-devel@alsa-project.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=jiaxin.yu@mediatek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=perex@perex.cz \
--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
all inboxes | Powered by JetHome®