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, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 5.10 000/270] 5.10.238-rc1 review
Date: Mon, 2 Jun 2025 22:37:18 +0200 [thread overview]
Message-ID: <aD4LfrY/mz3hdrCw@duo.ucw.cz> (raw)
In-Reply-To: <20250602134307.195171844@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1746 bytes --]
Hi!
> This is the start of the stable review cycle for the 5.10.238 release.
> There are 270 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.
We see build problem on risc-v:
drivers/clocksource/timer-riscv.c: In function 'riscv_timer_dying_cpu':
1932
drivers/clocksource/timer-riscv.c:82:2: error: implicit declaration of function 'riscv_clock_event_stop' [-Werror=implicit-function-declaration]
1933
82 | riscv_clock_event_stop();
1934
| ^~~~~~~~~~~~~~~~~~~~~~
1935
CC fs/namei.o
1936
CC net/sunrpc/rpcb_clnt.o
1937
cc1: some warnings being treated as errors
1938
make[2]: *** [scripts/Makefile.build:286: drivers/clocksource/timer-riscv.o] Error 1
1939
make[1]: *** [scripts/Makefile.build:503: drivers/clocksource] Error 2
1940
make[1]: *** Waiting for unfinished jobs....
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/1849177067
Huh. And on arm....?
drivers/clocksource/timer-riscv.c: In function 'riscv_timer_dying_cpu':
2053
drivers/clocksource/timer-riscv.c:82:2: error: implicit declaration of function 'riscv_clock_event_stop' [-Werror=implicit-function-declaration]
2054
82 | riscv_clock_event_stop();
2055
| ^~~~~~~~~~~~~~~~~~~~~~
2056
CC drivers/mmc/core/slot-gpio.o
2057
CC drivers/crypto/virtio/virtio_crypto_core.o
2058
CC drivers/firmware/efi/libstub/lib-cmdline.o
2059
cc1: some warnings being treated as errors
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
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-06-02 20:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 13:44 Greg Kroah-Hartman
2025-06-02 13:47 ` [PATCH 5.10 151/270] arm64/mm: Check PUD_TYPE_TABLE in pud_bad() Greg Kroah-Hartman
2025-06-02 16:49 ` [PATCH 5.10 000/270] 5.10.238-rc1 review Florian Fainelli
2025-06-02 16:50 ` Florian Fainelli
2025-06-03 7:58 ` Greg Kroah-Hartman
2025-06-03 16:00 ` Florian Fainelli
2025-06-04 8:06 ` Greg Kroah-Hartman
2025-06-04 18:29 ` Florian Fainelli
2025-06-02 20:37 ` Pavel Machek [this message]
2025-06-03 5:48 ` Naresh Kamboju
2025-06-03 7:57 ` Greg Kroah-Hartman
2025-06-03 9:45 ` Mark Brown
2025-06-03 10:06 ` Greg Kroah-Hartman
2025-06-03 10:46 ` Mark Brown
2025-06-04 8:09 ` Greg Kroah-Hartman
2025-06-04 9:40 ` 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=aD4LfrY/mz3hdrCw@duo.ucw.cz \
--to=pavel@denx.de \
--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=srw@sladewatkins.net \
--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®