[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20251106164840.c594ed684d22c97a6df7e364@linux-foundation.org>
Date: Thu, 6 Nov 2025 16:48:40 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Carlos Llamas <cmllamas@...gle.com>
Cc: "Matthieu Baerts (NGI0)" <matttbe@...nel.org>, Breno Leitao
<leitao@...ian.org>, Luca Ceresoli <luca.ceresoli@...tlin.com>, Miroslav
Benes <mbenes@...e.cz>, Mark Brown <broonie@...nel.org>, Puranjay Mohan
<puranjay@...nel.org>, Mark Rutland <mark.rutland@....com>, Catalin Marinas
<catalin.marinas@....com>, kernel-team@...roid.com,
linux-kernel@...r.kernel.org, Joe Perches <joe@...ches.com>
Subject: Re: [PATCH] scripts/decode_stacktrace.sh: fix build ID and PC
source parsing
On Thu, 6 Nov 2025 00:59:55 +0000 Carlos Llamas <cmllamas@...gle.com> wrote:
> > I view the Fixes: as a recommendation we make to -stable maintainers
> > saying "I think this should be backported to <here> and later". As
> > such, giving them multiple backporting targets must make their little
> > heads spin.
>
> So I've heard conflicting arguments about backporting patches to stable
> for these scripts. That's why I skipped the Cc: stable tag. IIRC, the
> argument is that one should always run the ToT scripts? <shrug>
Seems weird. Later scripts may use features which aren't present in
older kernels. Moreso with selftests, of course.
> You are right about the multiple Fixes: though. I should have only used:
>
> Fixes: 2bff77c665ed ("scripts/decode_stacktrace.sh: fix decoding of lines with an additional info")
Updated, thanks.
Powered by blists - more mailing lists