From: Greg KH <gregkh@linuxfoundation.org>
To: 陈华才 <chenhuacai@loongson.cn>
Cc: Miguel Ojeda <ojeda@kernel.org>,
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,
Tianyang Zhang <zhangtianyang@loongson.cn>
Subject: Re: Re: [PATCH 6.12 000/460] 6.12.78-rc1 review
Date: Fri, 27 Mar 2026 10:17:51 +0100 [thread overview]
Message-ID: <2026032736-reproach-dipper-f6bc@gregkh> (raw)
In-Reply-To: <7f616aa1.4eda2.19d27b31b8c.Coremail.chenhuacai@loongson.cn>
On Thu, Mar 26, 2026 at 09:12:22AM +0800, 陈华才 wrote:
> Hi, Greg, Sasha,
>
>
> > -----原始邮件-----
> > 发件人: "Miguel Ojeda" <ojeda@kernel.org>
> > 发送时间:2026-03-25 08:06:00 (星期三)
> > 收件人: gregkh@linuxfoundation.org
> > 抄送: 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@loongson.cn>, "Tianyang Zhang" <zhangtianyang@loongson.cn>
> > 主题: Re: [PATCH 6.12 000/460] 6.12.78-rc1 review
> >
> > On Mon, 23 Mar 2026 14:39:56 +0100 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> > >
> > > This is the start of the stable review cycle for the 6.12.78 release.
> > > There are 460 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 Wed, 25 Mar 2026 13:44:33 +0000.
> > > Anything received after that time might be too late.
> >
> > Boot-tested under QEMU for Rust x86_64, arm64 and riscv64; built-tested
> > for loongarch64:
> >
> > Tested-by: Miguel Ojeda <ojeda@kernel.org>
> >
> > loongarch64 failed to build for me:
> >
> > arch/loongarch/kernel/machine_kexec.c:139:13: error: static declaration of 'machine_kexec_mask_interrupts' follows non-static declaration
> > 139 | static void machine_kexec_mask_interrupts(void)
> > | ^
> > ./include/linux/irq.h:698:13: note: previous declaration is here
> > 698 | extern void machine_kexec_mask_interrupts(void);
> > | ^
> >
> > The `static void machine_kexec_mask_interrupts(void)` for loongarch64
> > was not removed because it was adjusted in:
> >
> > 429bf3f04c24 ("LoongArch: Add machine_kexec_mask_interrupts() implementation")
> Yes, 429bf3f04c24 ("LoongArch: Add machine_kexec_mask_interrupts() implementation")
> should be reverted for this version. But why you ignore Miguel's report?
Sorry, but your footer email:
> 本邮件及其附件含有龙芯中科的商业秘密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制或散发)本邮件及其附件中的信息。如果您错收本邮件,请您立即电话或邮件通知发件人并删除本邮件。
> This email and its attachments contain confidential information from Loongson Technology , which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it.
>
>
Caused me to miss this as my filters shove it aside :(
Anyway, my fault, I'll go take your revert now, and do a quick release
to resolve this issue, sorry about that. They "joys" of doing stable
releases while traveling at a conference at the same time...
greg k-h
next prev parent reply other threads:[~2026-03-27 9:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 13:39 [PATCH 6.12 000/460] 6.12.78-rc1 review Greg Kroah-Hartman
2026-03-23 15:20 ` Brett A C Sheffield
2026-03-23 17:58 ` Peter Schneider
2026-03-23 19:17 ` Pavel Machek
2026-03-23 20:38 ` Florian Fainelli
2026-03-23 22:09 ` Shuah Khan
2026-03-24 4:34 ` Harshit Mogalapalli
2026-03-24 8:24 ` Ron Economos
2026-03-24 9:00 ` Francesco Dolcini
2026-03-24 9:04 ` Jon Hunter
2026-03-24 15:03 ` Mark Brown
2026-03-25 0:06 ` Miguel Ojeda
2026-03-26 1:12 ` 陈华才
2026-03-27 9:17 ` Greg KH [this message]
2026-03-25 8:19 ` Barry K. Nathan
2026-03-25 10:57 ` Shung-Hsi Yu
2026-03-30 9:02 ` Guenter Roeck
2026-03-31 11:07 ` Greg Kroah-Hartman
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=2026032736-reproach-dipper-f6bc@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=chenhuacai@loongson.cn \
--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=ojeda@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 \
--cc=zhangtianyang@loongson.cn \
/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