From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
To: Charles Keepax <ckeepax@opensource.cirrus.com>, broonie@kernel.org
Cc: lgirdwood@gmail.com, yung-chuan.liao@linux.intel.com,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH 0/4] Series of SDCA bug fixes
Date: Wed, 22 Jul 2026 20:15:28 +0200 [thread overview]
Message-ID: <857b28b7-1ddd-41ad-b7fe-dbdcea3fbfc4@linux.dev> (raw)
In-Reply-To: <20260722103500.872714-1-ckeepax@opensource.cirrus.com>
On 7/22/26 12:34, Charles Keepax wrote:
> Fix up some error path and size checking issues in the SDCA code.
>
> Thanks,
> Charles
>
> Charles Keepax (4):
> ASoC: SDCA: Correct pointer passed to devm_acpi_table_put
> ASoC: SDCA: Always free firmware in FDL path
> ASoC: SDCA: Make UMP message size check more robust
> ASoC: SDCA: Ensure that Control Range is large enough for header
LGTM
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
>
> sound/soc/sdca/sdca_device.c | 2 +-
> sound/soc/sdca/sdca_fdl.c | 5 ++++-
> sound/soc/sdca/sdca_functions.c | 2 ++
> sound/soc/sdca/sdca_ump.c | 4 ++--
> 4 files changed, 9 insertions(+), 4 deletions(-)
>
next prev parent reply other threads:[~2026-07-23 17:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 10:34 [PATCH 0/4] Series of SDCA bug fixes Charles Keepax
2026-07-22 10:34 ` [PATCH 1/4] ASoC: SDCA: Correct pointer passed to devm_acpi_table_put Charles Keepax
2026-07-22 10:34 ` [PATCH 2/4] ASoC: SDCA: Always free firmware in FDL path Charles Keepax
2026-07-22 10:34 ` [PATCH 3/4] ASoC: SDCA: Make UMP message size check more robust Charles Keepax
2026-07-22 10:35 ` [PATCH 4/4] ASoC: SDCA: Ensure that Control Range is large enough for header Charles Keepax
2026-07-22 18:15 ` Pierre-Louis Bossart [this message]
2026-07-23 20:11 ` [PATCH 0/4] Series of SDCA bug fixes 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=857b28b7-1ddd-41ad-b7fe-dbdcea3fbfc4@linux.dev \
--to=pierre-louis.bossart@linux.dev \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox