public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 0/2] ASoC: topology: Fix loading topology issue
Date: Wed, 14 Aug 2024 16:49:25 +0200	[thread overview]
Message-ID: <2024081454-creature-subtype-9139@gregkh> (raw)
In-Reply-To: <351cb9f0-c016-43d2-a1f4-6635503aed56@linux.intel.com>

On Wed, Aug 14, 2024 at 04:19:06PM +0200, Amadeusz Sławiński wrote:
> On 8/14/2024 4:12 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
> > > 
> > > Amadeusz Sławiński (2):
> > >    ASoC: topology: Clean up route loading
> > >    ASoC: topology: Fix route memory corruption
> > > 
> > >   sound/soc/soc-topology.c | 32 ++++++++------------------------
> > >   1 file changed, 8 insertions(+), 24 deletions(-)
> > > 
> > > 
> > > base-commit: 878fbff41def4649a2884e9d33bb423f5a7726b0
> > > -- 
> > > 2.34.1
> > > 
> > > 
> > 
> > What stable tree(s) is this for?
> 
> For whichever one has 97ab304ecd95 ("ASoC: topology: Fix references to freed
> memory") applied and doesn't have following patches, as far as I can tell:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/sound?h=v6.9.12
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/sound/soc?h=v6.6.46
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/sound/soc?h=v6.1.105
> 
> should I send separate mail for each?

If they do not apply cleanly to all of them, yes.  If not, no.

Please resend these anyway, with the proper git id info so we don't have
to hand paste them in.

thanks,

greg k-h

  reply	other threads:[~2024-08-14 14:49 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 [this message]
2024-08-27 13:11 ` Greg Kroah-Hartman
2024-08-27 13:23   ` Amadeusz Sławiński

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=2024081454-creature-subtype-9139@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