public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel•org>
To: "Liam Girdwood" <lgirdwood@gmail•com>,
	"Takashi Iwai" <tiwai@suse•com>,
	"Jaroslav Kysela" <perex@perex•cz>,
	"Matthias Brugger" <matthias.bgg@gmail•com>,
	"AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora•com>,
	"Chen-Yu Tsai" <wenst@chromium•org>,
	"Shunli Wang" <shunli.wang@mediatek•com>,
	"Cássio Gabriel" <cassiogabrielcontato@gmail•com>
Cc: linux-sound@vger•kernel.org, linux-kernel@vger•kernel.org,
	 linux-arm-kernel@lists•infradead.org,
	linux-mediatek@lists•infradead.org,  notify@kernel•org,
	stable@vger•kernel.org
Subject: Re: [PATCH 0/2] ASoC: mediatek: mt8183: Fix probe resource cleanup
Date: Tue, 02 Jun 2026 16:11:11 +0100	[thread overview]
Message-ID: <178041307167.93058.8280968694103073134.b4-ty@b4> (raw)
In-Reply-To: <20260527-asoc-mt8183-probe-cleanup-v1-0-4f4f5593c8d1@gmail.com>

On Wed, 27 May 2026 10:41:47 -0300, Cássio Gabriel wrote:
> ASoC: mediatek: mt8183: Fix probe resource cleanup
> 
> The MT8183 AFE probe has two cleanup gaps that match issues
> recently fixed in newer MediaTek AFE drivers.
> 
> First, reserved memory assigned with of_reserved_mem_device_init()
> is never released on driver removal or later probe failures.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: mediatek: mt8183: Release reserved memory on cleanup
      https://git.kernel.org/broonie/sound/c/bee65e00c092
[2/2] ASoC: mediatek: mt8183: Check runtime resume during probe
      https://git.kernel.org/broonie/sound/c/f0334fbfd107

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



      parent reply	other threads:[~2026-06-03  7:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27 13:41 [PATCH 0/2] ASoC: mediatek: mt8183: Fix probe resource cleanup Cássio Gabriel
2026-05-27 13:41 ` [PATCH 1/2] ASoC: mediatek: mt8183: Release reserved memory on cleanup Cássio Gabriel
2026-05-27 13:41 ` [PATCH 2/2] ASoC: mediatek: mt8183: Check runtime resume during probe Cássio Gabriel
2026-06-02 15:11 ` 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=178041307167.93058.8280968694103073134.b4-ty@b4 \
    --to=broonie@kernel$(echo .)org \
    --cc=angelogioacchino.delregno@collabora$(echo .)com \
    --cc=cassiogabrielcontato@gmail$(echo .)com \
    --cc=lgirdwood@gmail$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-mediatek@lists$(echo .)infradead.org \
    --cc=linux-sound@vger$(echo .)kernel.org \
    --cc=matthias.bgg@gmail$(echo .)com \
    --cc=notify@kernel$(echo .)org \
    --cc=perex@perex$(echo .)cz \
    --cc=shunli.wang@mediatek$(echo .)com \
    --cc=stable@vger$(echo .)kernel.org \
    --cc=tiwai@suse$(echo .)com \
    --cc=wenst@chromium$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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