From: Miguel Ojeda <ojeda@kernel.org>
To: gregkh@linuxfoundation.org
Cc: achill@achill.org, akpm@linux-foundation.org, broonie@kernel.org,
conor@kernel.org, f.fainelli@gmail.com, hargar@microsoft.com,
jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
linux@roeck-us.net, lkft-triage@lists.linaro.org,
patches@kernelci.org, patches@lists.linux.dev,
pavel@nabladev.com, rwarsow@gmx.de, shuah@kernel.org,
sr@sladewatkins.com, stable@vger.kernel.org,
sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org,
Miguel Ojeda <ojeda@kernel.org>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
loongarch@lists.linux.dev, Benno Lossin <lossin@kernel.org>
Subject: Re: [PATCH 6.12 000/241] 6.12.81-rc2 review
Date: Fri, 10 Apr 2026 05:06:03 +0200 [thread overview]
Message-ID: <20260410030603.70733-1-ojeda@kernel.org> (raw)
In-Reply-To: <20260409091733.126574279@linuxfoundation.org>
On Thu, 09 Apr 2026 11:25:21 +0200 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.12.81 release.
> There are 241 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.
>
> Responses should be made by Sat, 11 Apr 2026 09:16:49 +0000.
> Anything received after that time might be too late.
Boot-tested under QEMU for Rust x86_64, arm64 and riscv64:
Tested-by: Miguel Ojeda <ojeda@kernel.org>
In loongarch64 I am seeing:
arch/loongarch/mm/tlb.c:292:19: error: use of undeclared identifier 'exception_handlers'; did you mean 'exception_table'?
292 | vec_sz = sizeof(exception_handlers);
| ^~~~~~~~~~~~~~~~~~
| exception_table
./arch/loongarch/include/asm/exception.h:9:14: note: 'exception_table' declared here
9 | extern void *exception_table[];
| ^
arch/loongarch/mm/tlb.c:292:18: error: invalid application of 'sizeof' to an incomplete type 'void *[]'
292 | vec_sz = sizeof(exception_handlers);
| ^~~~~~~~~~~~~~~~~~~~
Cc: Huacai Chen <chenhuacai@kernel.org>
Cc: WANG Xuerui <kernel@xen0n.name>
Cc: loongarch@lists.linux.dev
And then the many missing safety comments Clippy warnings we expected,
i.e. the ones that we discussed recently, e.g.:
warning: unsafe block missing a safety comment
--> rust/kernel/init/macros.rs:1015:25
Cc: Benno Lossin <lossin@kernel.org>
I hope this helps!
Cheers,
Miguel
next prev parent reply other threads:[~2026-04-10 3:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 9:25 [PATCH 6.12 000/241] 6.12.81-rc2 review Greg Kroah-Hartman
2026-04-09 14:01 ` Mark Brown
2026-04-09 17:15 ` Jon Hunter
2026-04-09 17:17 ` Pavel Machek
2026-04-09 18:16 ` Florian Fainelli
2026-04-09 18:46 ` Peter Schneider
2026-04-10 3:06 ` Miguel Ojeda [this message]
2026-04-10 13:29 ` 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=20260410030603.70733-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=loongarch@lists.linux.dev \
--cc=lossin@kernel.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 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.