From: Andrew Morton <akpm@linux-foundation.org>
To: Carlos Llamas <cmllamas@google.com>
Cc: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>,
Breno Leitao <leitao@debian.org>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Miroslav Benes <mbenes@suse.cz>, Mark Brown <broonie@kernel.org>,
Puranjay Mohan <puranjay@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
Joe Perches <joe@perches.com>
Subject: Re: [PATCH] scripts/decode_stacktrace.sh: fix build ID and PC source parsing
Date: Thu, 6 Nov 2025 16:48:40 -0800 [thread overview]
Message-ID: <20251106164840.c594ed684d22c97a6df7e364@linux-foundation.org> (raw)
In-Reply-To: <aQvzC6HqCrCKd2uK@google.com>
On Thu, 6 Nov 2025 00:59:55 +0000 Carlos Llamas <cmllamas@google.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.
prev parent reply other threads:[~2025-11-07 0:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 1:03 Carlos Llamas
2025-10-30 12:24 ` Matthieu Baerts
2025-10-30 14:50 ` Luca Ceresoli
2025-10-31 3:57 ` Andrew Morton
2025-11-06 0:59 ` Carlos Llamas
2025-11-07 0:48 ` Andrew Morton [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=20251106164840.c594ed684d22c97a6df7e364@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cmllamas@google.com \
--cc=joe@perches.com \
--cc=kernel-team@android.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=mark.rutland@arm.com \
--cc=matttbe@kernel.org \
--cc=mbenes@suse.cz \
--cc=puranjay@kernel.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
all inboxes | Powered by JetHome®