From: phucduc.bui@gmail.com
To: Mark Brown <broonie@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Cezary Rojewski <cezary.rojewski@intel.com>,
linux-sound@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
bui duc phuc <phucduc.bui@gmail.com>
Subject: [PATCH v3 0/3] ASoC: mediatek: mt6797: Fix error handling
Date: Fri, 21 Aug 2026 19:28:37 +0700 [thread overview]
Message-ID: <20260821122840.41266-1-phucduc.bui@gmail.com> (raw)
From: bui duc phuc <phucduc.bui@gmail.com>
Hi all,
This series fixes and cleans up error handling in the MT6797 ASoC driver.
Compile tested only.
Changes in v2:
- Update the subject prefix from ASoC: mt6797: to ASoC: mediatek: mt6797:.
Changes in v3:
- Add a cover letter.
- Add Fixes tags.
- Add Reviewed-by tags.
Thanks,
Phuc
bui duc phuc (3):
ASoC: mediatek: mt6797: fix wrong unwind order and error code in
enable_clock
ASoC: mediatek: mt6797: Use dev_err_probe() for error handling
ASoC: mediatek: mt6797: Drop redundant probe error messages
sound/soc/mediatek/mt6797/mt6797-afe-clk.c | 23 +++++++++-------------
sound/soc/mediatek/mt6797/mt6797-afe-pcm.c | 8 ++------
2 files changed, 11 insertions(+), 20 deletions(-)
--
2.43.0
next reply other threads:[~2026-08-21 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 12:28 phucduc.bui [this message]
2026-08-21 12:28 ` [PATCH v3 1/3] ASoC: mediatek: mt6797: fix wrong unwind order and error code in enable_clock phucduc.bui
2026-08-21 12:28 ` [PATCH v3 2/3] ASoC: mediatek: mt6797: Use dev_err_probe() for error handling phucduc.bui
2026-08-21 12:28 ` [PATCH v3 3/3] ASoC: mediatek: mt6797: Drop redundant probe error messages phucduc.bui
2026-09-08 14:18 ` [PATCH v3 0/3] ASoC: mediatek: mt6797: Fix error handling 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=20260821122840.41266-1-phucduc.bui@gmail.com \
--to=phucduc.bui@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.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=linux-sound@vger.kernel.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 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.