public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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 0/2] ASoC: topology: Fix loading topology issue
Date: Tue, 27 Aug 2024 15:23:04 +0200	[thread overview]
Message-ID: <1e9cd9d1-17c8-4603-ab95-d6996c5b4eca@linux.intel.com> (raw)
In-Reply-To: <2024082729-subatomic-anemia-003d@gregkh>

On 8/27/2024 3:11 PM, Greg Kroah-Hartman wrote:
> On Wed, Aug 14, 2024 at 04:06:55PM +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
> 
> You need to put the git ids in the patches directly do we have a clue
> what to do.
> 
> Also, what tree(s) do you need/want these in?
> 
> Please fix up and resend.
> 

I've already send v2 and as far as I know it was merged.

Here is link to v2:
https://lore.kernel.org/linux-sound/2024081442-thimble-widget-e370@gregkh/T/#t

      reply	other threads:[~2024-08-27 13:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 14:06 [PATCH for stable 0/2] ASoC: topology: Fix loading topology issue Amadeusz Sławiński
2024-08-14 14:06 ` [PATCH for stable 1/2] ASoC: topology: Clean up route loading Amadeusz Sławiński
2024-08-14 14:12   ` Greg Kroah-Hartman
2024-08-14 14:20     ` Amadeusz Sławiński
2024-08-27 13:11   ` Greg Kroah-Hartman
2024-08-14 14:06 ` [PATCH for stable 2/2] ASoC: topology: Fix route memory corruption Amadeusz Sławiński
2024-08-14 14:20   ` Amadeusz Sławiński
2024-08-14 14:12 ` [PATCH for stable 0/2] ASoC: topology: Fix loading topology issue Greg Kroah-Hartman
2024-08-14 14:19   ` Amadeusz Sławiński
2024-08-14 14:49     ` Greg Kroah-Hartman
2024-08-27 13:11 ` Greg Kroah-Hartman
2024-08-27 13:23   ` Amadeusz Sławiński [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=1e9cd9d1-17c8-4603-ab95-d6996c5b4eca@linux.intel.com \
    --to=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=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