Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	 patches@opensource.cirrus.com
Subject: Re: [PATCH] ASoC: cs-amp-lib: Replace __free(kfree) with normal kfree() cleanup
Date: Thu, 18 Dec 2025 08:21:05 +0000	[thread overview]
Message-ID: <176604606576.48417.12415715226763234194.b4-ty@kernel.org> (raw)
In-Reply-To: <20251201123906.86876-1-rf@opensource.cirrus.com>

On Mon, 01 Dec 2025 12:39:06 +0000, Richard Fitzgerald wrote:
> Replace the use of __free(kfree) in _cs_amp_set_efi_calibration_data()
> with normal kfree() at the end of the function.
> 
> Krzysztof Kozlowski pointed out that __free() can be dangerous.
> It can introduce new cleanup bugs. These are more subtle and difficult to
> spot than a missing goto in traditional cleanup, because they are triggered
> by writing regular idiomatic C code instead of using C++ conventions. As
> it's regular C style it's more likely to be missed because the code is as
> would be expected for C. The traditional goto also more obviously flags
> to anyone changing the code in the future that they must be careful about
> the cleanup.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: cs-amp-lib: Replace __free(kfree) with normal kfree() cleanup
      commit: 9a123f222e1889d020d873aa6e0799098d22cdb1

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark


      reply	other threads:[~2025-12-18  8:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01 12:39 [PATCH] ASoC: cs-amp-lib: Replace __free(kfree) with normal kfree() cleanup Richard Fitzgerald
2025-12-18  8:21 ` Mark Brown [this message]

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=176604606576.48417.12415715226763234194.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.cirrus.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