From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pavel Machek <pavel@denx.de>
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.4 00/94] 5.4.290-rc2 review
Date: Sat, 1 Feb 2025 09:01:58 +0100 [thread overview]
Message-ID: <2025020157-unsecured-map-aa0c@gregkh> (raw)
In-Reply-To: <Z5zIZHIZxuHoymof@duo.ucw.cz>
On Fri, Jan 31, 2025 at 01:56:04PM +0100, Pavel Machek wrote:
> Hi!
>
> > This is the start of the stable review cycle for the 5.4.290 release.
> > There are 94 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.
>
> Still not ok.
>
> In file included from ./arch/riscv/include/asm/ptrace.h:10,
> 1128
> from ./arch/riscv/include/asm/processor.h:11,
> 1129
> from ./arch/riscv/include/asm/irqflags.h:10,
> 1130
> from ./include/linux/irqflags.h:16,
> 1131
> from ./arch/riscv/include/asm/bitops.h:14,
> 1132
> from ./include/linux/bitops.h:27,
> 1133
> from ./include/linux/kernel.h:12,
> 1134
> from ./include/linux/list.h:9,
> 1135
> from ./include/linux/kobject.h:19,
> 1136
> from ./include/linux/device.h:16,
> 1137
> from ./include/linux/node.h:18,
> 1138
> from ./include/linux/cpu.h:17,
> 1139
> from arch/riscv/kernel/traps.c:6:
> 1140
> arch/riscv/kernel/traps.c: In function 'trap_init':
> 1141
> arch/riscv/kernel/traps.c:164:23: error: 'handle_exception' undeclared (first use in this function)
> 1142
> 164 | csr_write(CSR_TVEC, &handle_exception);
> 1143
> | ^~~~~~~~~~~~~~~~
> 1144
> ./arch/riscv/include/asm/csr.h:166:38: note: in definition of macro 'csr_write'
> 1145
> 166 | unsigned long __v = (unsigned long)(val); \
> 1146
> | ^~~
> 1147
What's it with the blank lines?
Anyway, are you all really caring about riscv on a 5.4.y kernel? Last I
checked, the riscv maintainers said not to even use that kernel for that
architecture. Do you all have real boards that care about this kernel
tree that you are insisting on keeping alive? Why not move them to a
newer LTS kernel?
thanks,
greg k-h
next prev parent reply other threads:[~2025-02-01 8:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 11:21 [PATCH 5.4 00/94] 5.4.290-rc2 review Greg Kroah-Hartman
2025-01-31 12:56 ` Pavel Machek
2025-02-01 8:01 ` Greg Kroah-Hartman [this message]
2025-02-01 13:30 ` Guenter Roeck
2025-02-01 15:03 ` Guenter Roeck
2025-02-01 15:34 ` Greg Kroah-Hartman
2025-01-31 13:36 ` Jon Hunter
2025-01-31 17:22 ` Muhammad Usama Anjum
2025-02-01 15:08 ` Naresh Kamboju
2025-02-01 15:34 ` Greg Kroah-Hartman
2025-02-01 15:43 ` Guenter Roeck
2025-02-02 13:31 ` Harshit Mogalapalli
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=2025020157-unsecured-map-aa0c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.