From: Sasha Levin <sashal@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: Sasha Levin <sashal@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,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH 6.12 000/666] 6.12.91-rc1 review
Date: Thu, 21 May 2026 08:55:48 -0400 [thread overview]
Message-ID: <20260521-6.12.91-libbpf-drop-sashal@kernel.org> (raw)
In-Reply-To: <54f12da1-32e2-48dc-bf84-3bdaf8ef0f6a@gmail.com>
On Wed, May 20, 2026 at 02:46:48PM -0700, Florian Fainelli wrote:
> perf fails to build on ARM/ARM64/MIPS with:
> [...]
> libbpf.c:1538:76: error: implicit declaration of function 'errstr';
> [...]
> we would need to backport the below commit, but it does not apply
> cleanly to 6.12.y:
>
> commit c68b6fdc3600466e3c265bad34d099eb8c5280f1
> libbpf: move libbpf_errstr() into libbpf_utils.c
Dropped 271abf041cb3 ("libbpf: Stringify errno in log messages in
libbpf.c") from the 6.12 queue, along with its two dep-of companions
(libbpf: Prevent double close and leak of btf objects; libbpf: Change
log level of btf loading error message), since c68b6fdc3600 doesn't
apply without a larger libbpf refactor coming along.
Thanks for the report.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-05-21 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 16:13 Greg Kroah-Hartman
2026-05-20 16:15 ` [PATCH 6.12 110/666] Bluetooth: SCO: check for codecs->num_codecs == 1 before assigning to sco_pi(sk)->codec Greg Kroah-Hartman
2026-05-20 19:11 ` [PATCH 6.12 000/666] 6.12.91-rc1 review Brett A C Sheffield
2026-05-20 21:46 ` Florian Fainelli
2026-05-21 12:55 ` Sasha Levin [this message]
2026-05-21 5:17 ` Francesco Dolcini
2026-05-21 9:55 ` Pavel Machek
2026-05-21 10:36 ` Mark Brown
2026-05-21 23:51 ` Ron Economos
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=20260521-6.12.91-libbpf-drop-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
Powered by JetHome