From: Florian Fainelli <f.fainelli@gmail.com>
To: Mark Brown <broonie@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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@denx.de, jonathanh@nvidia.com, sudipm.mukherjee@gmail.com,
rwarsow@gmx.de, conor@kernel.org, hargar@microsoft.com,
achill@achill.org, sr@sladewatkins.com
Subject: Re: [PATCH 5.15 000/392] 5.15.197-rc1 review
Date: Wed, 3 Dec 2025 10:51:17 -0800 [thread overview]
Message-ID: <b4d4d33e-07d8-4868-abc5-4161a63bb948@gmail.com> (raw)
In-Reply-To: <41e4124d-8cb3-44b9-871b-8fa64b54b303@sirena.org.uk>
On 12/3/25 10:46, Mark Brown wrote:
> On Wed, Dec 03, 2025 at 04:22:30PM +0100, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 5.15.197 release.
>> There are 392 patches in this series, all will be posted as a response
>> to this one. If anyone has any issues with these being applied, please
>> let me know.
>
> I'm seeing a build failure in the KVM selftests on arm64 with this, due
> to dddac591bc98 (tools bitmap: Add missing asm-generic/bitsperlong.h
> include):
>
> aarch64-linux-gnu-gcc -Wall -Wstrict-prototypes -Wuninitialized -O2 -g -std=gnu9
> 9 -fno-stack-protector -fno-PIE -I../../../../tools/include -I../../../../tools/
> arch/arm64/include -I../../../../usr/include/ -Iinclude -I. -Iinclude/aarch64 -I
> .. -pthread -no-pie dirty_log_perf_test.c /build/stage/build-work/kselftes
> t/kvm/libkvm.a -o /build/stage/build-work/kselftest/kvm/dirty_log_perf_test
> In file included from ../../../../tools/include/linux/bitmap.h:6,
> from dirty_log_perf_test.c:15:
> ../../../../tools/include/asm-generic/bitsperlong.h:14:2: error: #error Inconsis
> tent word size. Check asm/bitsperlong.h
> 14 | #error Inconsistent word size. Check asm/bitsperlong.h
> | ^~~~~
> In file included from ../../../../usr/include/asm-generic/int-ll64.h:12,
> from ../../../../usr/include/asm-generic/types.h:7,
> from ../../../../usr/include/asm/types.h:1,
> from ../../../../tools/include/linux/bitops.h:5,
> from ../../../../tools/include/linux/bitmap.h:8:
> ../../../../usr/include/asm/bitsperlong.h:20:9: warning: "__BITS_PER_LONG" redefined
> 20 | #define __BITS_PER_LONG 64
> | ^~~~~~~~~~~~~~~
> In file included from ../../../../tools/include/asm-generic/bitsperlong.h:5:
> ../../../../tools/include/uapi/asm-generic/bitsperlong.h:12:9: note: this is the location of the previous definition
> 12 | #define __BITS_PER_LONG 32
> | ^~~~~~~~~~~~~~~
Yes this also affects building "perf".
--
Florian
next prev parent reply other threads:[~2025-12-03 18:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 15:22 Greg Kroah-Hartman
2025-12-03 17:51 ` Florian Fainelli
2025-12-04 16:36 ` Greg Kroah-Hartman
2025-12-03 18:46 ` Mark Brown
2025-12-03 18:51 ` Florian Fainelli [this message]
2025-12-04 16:31 ` Greg Kroah-Hartman
2025-12-04 16:41 ` Ian Rogers
2025-12-03 19:40 ` Jon Hunter
2025-12-04 16:34 ` Greg Kroah-Hartman
2025-12-03 23:07 ` Hardik Garg
2025-12-04 0:01 ` Shuah Khan
2025-12-04 8:38 ` Naresh Kamboju
2025-12-04 16:36 ` Greg Kroah-Hartman
2025-12-04 14:07 ` Ron Economos
2025-12-10 16:48 ` Jeffrin Thalakkottoor
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=b4d4d33e-07d8-4868-abc5-4161a63bb948@gmail.com \
--to=f.fainelli@gmail.com \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--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@denx.de \
--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®