From: Pavel Machek <pavel@denx.de>
To: 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,
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
Subject: Re: [PATCH 5.10 000/332] 5.10.246-rc1 review
Date: Tue, 28 Oct 2025 09:03:23 +0100 [thread overview]
Message-ID: <aQB4yznImF+00KSo@duo.ucw.cz> (raw)
In-Reply-To: <20251027183524.611456697@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
Hi!
> This is the start of the stable review cycle for the 5.10.246 release.
> There are 332 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 failures on risc-v:
arch/riscv/kernel/cpu.c: In function 'riscv_of_processor_hartid':
2246
arch/riscv/kernel/cpu.c:24:26: error: implicit declaration of function 'of_get_cpu_hwid'; did you mean 'of_get_cpu_node'? [-Werror=implicit-function-declaration]
2247
24 | *hart = (unsigned long) of_get_cpu_hwid(node, 0);
2248
| ^~~~~~~~~~~~~~~
2249
| of_get_cpu_node
2250
arch/riscv/kernel/cpufeature.c: In function 'riscv_fill_hwcap':
2251
arch/riscv/kernel/cpufeature.c:107:16: warning: unused variable 'ext_end' [-Wunused-variable]
2252
107 | const char *ext_end = isa;
2253
| ^~~~~~~
2254
cc1: some warnings being treated as errors
2255
make[2]: *** [scripts/Makefile.build:286: arch/riscv/kernel/cpu.o] Error 1
2256
make[2]: *** Waiting for unfinished jobs....
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/11870647387
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/2123716079
Best regards,
Pavel
--
In cooperation with DENX Software Engineering GmbH, HRB 165235 Munich,
Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2025-10-28 8:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 18:30 [PATCH 5.10 000/332] 5.10.246-rc1 review Greg Kroah-Hartman
2025-10-27 18:32 ` [PATCH 5.10 115/332] tools build: Align warning options with perf Greg Kroah-Hartman
2025-10-27 18:35 ` [PATCH 5.10 278/332] arm64, mm: avoid always making PTE dirty in pte_mkwrite() Greg Kroah-Hartman
2025-10-27 20:42 ` [PATCH 5.10 000/332] 5.10.246-rc1 review Florian Fainelli
2025-10-27 23:23 ` Slade Watkins
2025-10-28 6:19 ` Dominique Martinet
2025-10-28 8:03 ` Pavel Machek [this message]
2025-10-28 11:28 ` Jon Hunter
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=aQB4yznImF+00KSo@duo.ucw.cz \
--to=pavel@denx.de \
--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=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