From: Sasha Levin <sashal@kernel.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Sasha Levin <sashal@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com, Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Jiri Slaby <jirislaby@kernel.org>
Subject: Re: [PATCH 7.3 0000/2651] 7.3.6-rc1 review
Date: Thu, 19 Nov 2026 21:09:02 -0500 [thread overview]
Message-ID: <20261120020908.2320910-5-sashal@kernel.org> (raw)
In-Reply-To: <b1aecdb0-5076-4df1-82a0-e4f5dc755578@leemhuis.info>
On Thu, Nov 19, 2026 at 08:03:14AM +0100, Thorsten Leemhuis wrote:
> lore I was able to fix this on 7.3.y-rc by cherry-picking 3dfdd195c7e45f
> ("perf dwarf-aux: Add die_same_file() and die_get_type_die()") [v7.4-rc1].
Following up on my earlier reply: 14ca0a28de37 ("perf annotate-data: Resolve
type DIEs in the debug file they came from") is dropped from the 6.18 and 6.12
queues as I said. 7.3 keeps it, with 3dfdd195c7e4 queued ahead of it.
> cherry-picking fc076b5f4807a3 ("perf trace: Introduce kernel symbol
> beautifier for virtual addresses") [v7.4-rc1]
c6dd6161815d ("perf trace: Enhance BTF type formatting to symbolise kernel
function pointers") turned out to be a prerequisite of 024b219744a9 ("perf
trace: Add upper bound checks for augmented BTF struct printing"), so both are
dropped from the 7.3, 6.18 and 6.12 queues.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-11-20 2:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 14:20 Greg Kroah-Hartman
2026-11-18 16:59 ` Brett A C Sheffield
2026-11-18 17:17 ` Pavel Machek
2026-11-18 19:02 ` Thorsten Leemhuis
2026-11-18 20:39 ` Gary Guo
2026-11-19 3:23 ` Alice C. Munduruca
2026-11-20 2:08 ` Sasha Levin
2026-11-18 19:08 ` Thorsten Leemhuis
2026-11-19 7:03 ` Thorsten Leemhuis
2026-11-19 16:08 ` Sasha Levin
2026-11-20 2:09 ` Sasha Levin [this message]
2026-11-18 19:59 ` Florian Fainelli
2026-11-18 22:30 ` Takeshi Ogasawara
2026-11-19 3:32 ` Peter Schneider
2026-11-19 7:11 ` Joungmin Lee
2026-11-19 15:37 ` Shuah Khan
2026-11-19 16:10 ` Markus Reichelt
2026-11-19 3:26 Sergey Lebedev
2026-11-19 16:08 ` 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=20261120020908.2320910-5-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=achill@achill.org \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jirislaby@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=namhyung@kernel.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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®