From: Sasha Levin <sashal@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
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,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 5.15 0000/2214] 5.15.226-rc1 review
Date: Thu, 19 Nov 2026 21:09:03 -0500 [thread overview]
Message-ID: <20261120020908.2320910-6-sashal@kernel.org> (raw)
In-Reply-To: <65c24a95-1087-4f30-9f9c-9e8636da211c@gmail.com>
On Wed, Nov 18, 2026 at 11:16:34AM -0800, Florian Fainelli wrote:
> undefined reference to `__evsel__parse_sample'
Here is where this stands for the perf failures you reported across the
trees:
- 5.15, 6.1 and 6.6 link failure: both evsel validation patches,
2148e094671b ("perf evsel: Validate branch stack before byte
swapping") and 02f6847e1822 ("perf evsel: Validate RAW sample before
byte swapping"), add tests that call __evsel__parse_sample(),
evsel__put() and perf_sample__exit(), which those trees (and partly
6.12 and 6.18) do not have. Both are dropped from 6.18, 6.12, 6.6,
6.1 and 5.15; 5.15 also loses 63c12ae2f246 ("perf evsel: Add
bitfield_swap() to handle branch_stack endian issue"), which was
queued for them. 7.3 keeps them.
- 6.6 dso__symbols: 45d15e89a783 ("perf symbols: Don't let a module's
last symbol overlap the next module") is dropped from 6.6.
- 5.10 jitdump in_pidns: 67dec9269314 ("perf inject jit: Add
namespaces support") and the four jitdump patches queued on top of
it (dc67c7837a83, 9bef5cead63d, 4eddf7d9e341, 92d50319b4f0) are
dropped from 5.10.
- 6.12 and 6.18 annotate-data: 14ca0a28de37 ("perf annotate-data:
Resolve type DIEs in the debug file they came from") is dropped from
6.18 and 6.12; 7.3 got the missing prerequisite instead.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-11-20 2:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 14:27 Greg Kroah-Hartman
2026-11-18 14:52 ` [PATCH 5.15 1473/2214] crypto: amlogic - Fix dma_map_sg error check Greg Kroah-Hartman
2026-11-18 15:04 ` [PATCH 5.15 2208/2214] dmaengine: dw-axi-dmac: Fix uninitialized variable in axi_chan_block_xfer_start() Greg Kroah-Hartman
2026-11-18 16:44 ` [PATCH 5.15 0000/2214] 5.15.226-rc1 review Brett A C Sheffield
2026-11-18 17:14 ` Pavel Machek
2026-11-18 19:16 ` Florian Fainelli
2026-11-20 2:09 ` Sasha Levin [this message]
2026-11-19 7:04 ` Richard Narron
2026-11-19 12:20 ` Barry K. Nathan
2026-11-19 15:51 ` Shuah Khan
2026-11-19 23:28 ` Richard Narron
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-6-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=achill@achill.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=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.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®