From: Sasha Levin <sashal@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: "Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
"Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
"Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
"Mark Brown" <broonie@kernel.org>,
lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
linux-sound@vger.kernel.org,
"Linux kernel regressions list" <regressions@lists.linux.dev>,
"Vitaly Chikunov" <vt@altlinux.org>,
stable@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 6.9 17/40] ASoC: topology: Fix route memory corruption
Date: Tue, 13 Aug 2024 22:18:50 -0400 [thread overview]
Message-ID: <ZrwUCnrtKQ61LWFS@sashalap> (raw)
In-Reply-To: <e95a876a-b4b4-4a9d-9608-ec27a9db3e0c@leemhuis.info>
On Mon, Aug 12, 2024 at 11:53:17AM +0200, Thorsten Leemhuis wrote:
>Hi, top-posting for once, to make this easily accessible to everyone.
>
>Greg, Sasha, to me it looks like something fell through the cracks.
>Pierre-Louis afaics about a week ago asked (see the quote below) to
>revert 97ab304ecd95c0 ("ASoC: topology: Fix references to freed memory")
>[v6.10-rc6, v6.9.11, v6.6.42, v6.1.101] from the stable branches *or*
>pick up b9dd212b14d27a ("ASoC: topology: Fix route memory corruption").
>But nothing like that has happened yet and I can't see any of those
>resolutions in the 6.6 queue.
>
>Side note: I have a very strong feeling that I'm missing or
>misunderstood something, but I decided to send this mail despite this...
>If something like that was the case: apologies in advance.
For AUTOSEL mails, I only end up looking at the threads when I'm about
to actually queue those commits up into the stable-queue, which is what
happened here.
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-08-14 2:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 16:17 [PATCH AUTOSEL 6.9 17/40] ASoC: topology: Fix route memory corruption Vitaly Chikunov
2024-08-05 17:09 ` Pierre-Louis Bossart
2024-08-12 9:53 ` Thorsten Leemhuis
2024-08-12 10:01 ` Amadeusz Sławiński
2024-08-12 10:25 ` Greg Kroah-Hartman
2024-08-12 10:38 ` Vitaly Chikunov
2024-08-12 14:11 ` Greg Kroah-Hartman
2024-08-13 14:42 ` Amadeusz Sławiński
2024-08-14 0:00 ` Vitaly Chikunov
2024-08-14 10:33 ` Mark Brown
2024-08-14 14:07 ` Amadeusz Sławiński
2024-08-12 10:24 ` Greg Kroah-Hartman
2024-08-14 2:18 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-09 16:18 [PATCH AUTOSEL 6.9 01/40] workqueue: Refactor worker ID formatting and make wq_worker_comm() use full ID string Sasha Levin
2024-07-09 16:18 ` [PATCH AUTOSEL 6.9 17/40] ASoC: topology: Fix route memory corruption Sasha Levin
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=ZrwUCnrtKQ61LWFS@sashalap \
--to=sashal@kernel.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.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=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