All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
To: Mark Brown <broonie@kernel.org>, Vitaly Chikunov <vt@altlinux.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org,
	"Thorsten Leemhuis" <regressions@leemhuis.info>,
	"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
	"Sasha Levin" <sashal@kernel.org>,
	linux-kernel@vger.kernel.org,
	"Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>,
	lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
	linux-sound@vger.kernel.org,
	"Linux kernel regressions list" <regressions@lists.linux.dev>
Subject: Re: [PATCH AUTOSEL 6.9 17/40] ASoC: topology: Fix route memory corruption
Date: Wed, 14 Aug 2024 16:07:55 +0200	[thread overview]
Message-ID: <1ea93e69-80da-4dc3-b63c-217b1f9f0447@linux.intel.com> (raw)
In-Reply-To: <e7b0597c-72d8-4cb6-bcec-19e29c1b864e@sirena.org.uk>

On 8/14/2024 12:33 PM, Mark Brown wrote:
> On Wed, Aug 14, 2024 at 03:00:53AM +0300, Vitaly Chikunov wrote:
>> On Tue, Aug 13, 2024 at 04:42:04PM +0200, Amadeusz Sławiński wrote:
> 
>>> Should this be cherry-pick of both (they should apply cleanly):
>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/sound/soc/soc-topology.c?id=e0e7bc2cbee93778c4ad7d9a792d425ffb5af6f7
>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/sound/soc/soc-topology.c?id=0298f51652be47b79780833e0b63194e1231fa34
>>> or just the second one adjusted to apply for stable trees?
> 
>> I think having commit with memory corruption fix is more important to
>> stable kernels than not having the code cleanup commit. So, I would
>> suggest stable policy to be changed a bit, and minor commits like this
>> code cleanup, be allowed in stable if they are dependence of bug fixing
>> commits.
> 
>> Additionally, these neutral commits just make stable trees become closer
>> to mainline trees (which allows more bug fix commits to be applied
>> cleanly).
> 
> The reason I nacked the cleanup commit was just that there was no
> indication that it was a dependency or anything, it just looked like
> standard stuff with not reviewing bot output.

I've send both patches for stable in 
https://lore.kernel.org/linux-sound/20240814140657.2369433-1-amadeuszx.slawinski@linux.intel.com/T/#t

  reply	other threads:[~2024-08-14 14:08 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 [this message]
2024-08-12 10:24     ` Greg Kroah-Hartman
2024-08-14  2:18     ` Sasha Levin
  -- 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=1ea93e69-80da-4dc3-b63c-217b1f9f0447@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.