From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
Cc: stable@vger.kernel.org, "Sasha Levin" <sashal@kernel.org>,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
"Linux kernel regressions list" <regressions@lists.linux.dev>,
tiwai@suse.com, perex@perex.cz, lgirdwood@gmail.com,
"Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
"Thorsten Leemhuis" <regressions@leemhuis.info>,
"Vitaly Chikunov" <vt@altlinux.org>,
"Mark Brown" <broonie@kernel.org>
Subject: Re: [PATCH for stable v2 0/2] ASoC: topology: Fix loading topology issue
Date: Wed, 14 Aug 2024 19:55:12 +0200 [thread overview]
Message-ID: <2024081442-thimble-widget-e370@gregkh> (raw)
In-Reply-To: <20240814154749.2723275-1-amadeuszx.slawinski@linux.intel.com>
On Wed, Aug 14, 2024 at 05:47:47PM +0200, Amadeusz Sławiński wrote:
> Commit 97ab304ecd95 ("ASoC: topology: Fix references to freed memory")
> is a problematic fix for issue in topology loading code, which was
> cherry-picked to stable. It was later corrected in
> 0298f51652be ("ASoC: topology: Fix route memory corruption"), however to
> apply cleanly e0e7bc2cbee9 ("ASoC: topology: Clean up route loading")
> also needs to be applied.
>
> Link: https://lore.kernel.org/linux-sound/ZrwUCnrtKQ61LWFS@sashalap/T/#mbfd273adf86fe93b208721f1437d36e5d2a9aa19
>
> Should be applied to stable 6.1, 6.6, 6.9.
6.9 is long end-of-life (as shown on the front page of kernel.org.)
Patches queued up to 6.1 and 6.6 now, thanks.
greg k-h
prev parent reply other threads:[~2024-08-14 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 15:47 [PATCH for stable v2 0/2] ASoC: topology: Fix loading topology issue Amadeusz Sławiński
2024-08-14 15:47 ` [PATCH for stable v2 1/2] ASoC: topology: Clean up route loading Amadeusz Sławiński
2024-08-14 15:47 ` [PATCH for stable v2 2/2] ASoC: topology: Fix route memory corruption Amadeusz Sławiński
2024-08-14 17:55 ` Greg Kroah-Hartman [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=2024081442-thimble-widget-e370@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=vt@altlinux.org \
/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;
as well as URLs for NNTP newsgroup(s).