From: phucduc.bui@gmail.com
To: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Olivier Moysan <olivier.moysan@foss.st.com>,
Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: linux-stm32@st-md-mailman.stormreply.com,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
bui duc phuc <phucduc.bui@gmail.com>
Subject: [PATCH 0/4] ASoC: stm: Drop redundant error message
Date: Mon, 20 Jul 2026 14:40:39 +0700 [thread overview]
Message-ID: <20260720074044.87528-1-phucduc.bui@gmail.com> (raw)
From: bui duc phuc <phucduc.bui@gmail.com>
Hi all,
This series removes redundant error messages across multiple STM32 ASoC
drivers. Since core functions already log failures internally, dropping
these explicit dev_err() blocks prevents duplicate log messages and
cleans up the code.
Compile-tested only.
Best regards,
Phuc
bui duc phuc (4):
ASoC: stm: stm32_adfsdm: Drop redundant error message
ASoC: stm: stm32_i2s: Drop redundant error messages
ASoC: stm: stm32_sai_sub: Drop redundant error messages
ASoC: stm: stm32_spdifrx: Drop redundant error messages
sound/soc/stm/stm32_adfsdm.c | 5 +----
sound/soc/stm/stm32_i2s.c | 6 ++----
sound/soc/stm/stm32_sai_sub.c | 8 ++------
sound/soc/stm/stm32_spdifrx.c | 6 ++----
4 files changed, 7 insertions(+), 18 deletions(-)
--
2.43.0
next reply other threads:[~2026-07-20 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 7:40 phucduc.bui [this message]
2026-07-20 7:40 ` [PATCH 1/4] ASoC: stm: stm32_adfsdm: Drop redundant error message phucduc.bui
2026-07-20 7:40 ` [PATCH 2/4] ASoC: stm: stm32_i2s: Drop redundant error messages phucduc.bui
2026-07-20 7:40 ` [PATCH 3/4] ASoC: stm: stm32_sai_sub: " phucduc.bui
2026-07-20 7:40 ` [PATCH 4/4] ASoC: stm: stm32_spdifrx: " phucduc.bui
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=20260720074044.87528-1-phucduc.bui@gmail.com \
--to=phucduc.bui@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=arnaud.pouliquen@foss.st.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=olivier.moysan@foss.st.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