From: Xi Ruoyao <xry111@xry111.site>
To: Guenter Roeck <linux@roeck-us.net>, Huacai Chen <chenhuacai@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Huacai Chen <chenhuacai@loongson.cn>,
loongarch@lists.linux.dev, Xuefeng Li <lixuefeng@loongson.cn>,
Guo Ren <guoren@kernel.org>, Xuerui Wang <kernel@xen0n.name>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Binbin Zhou <zhoubinbin@loongson.cn>
Subject: Re: [PATCH V2] LoongArch: Align ACPI structures if ARCH_STRICT_ALIGN enabled
Date: Sat, 25 Oct 2025 21:02:45 +0800 [thread overview]
Message-ID: <274fe4e6ff05401bc43d952efe69908fe052d875.camel@xry111.site> (raw)
In-Reply-To: <0104bccd-d3a2-4f6b-8838-0acf0563c4b6@roeck-us.net>
On Fri, 2025-09-26 at 11:27 -0700, Guenter Roeck wrote:
> > > I see that the patch made it into the upstream kernel, now breaking both
> > > mainline and 6.16.y test builds of loongarch64:allmodconfig with gcc.
> > >
> > > Since this is apparently intentional, I'll stop build testing
> > > loongarch64:allmodconfig. So far it looks like my qemu tests
> > > are not affected, so I'll continue testing those for the time being.
> >
> > See https://gcc.gnu.org/PR122073 and
> > https://github.com/acpica/acpica/pull/1050.
> >
>
> I understand that. Every compiler has bugs. Normally workarounds are implemented.
> Since that won't happen here, my remedy is to stop testing the affected
> configuration(s). I do this whenever I learn that a known problem won't be fixed.
> The above is not a complaint, just an information.
Hi Guenter,
The mainline should be already fixed with 6e3a4754717a ("ACPICA: Work
around bogus -Wstringop-overread warning since GCC 11") now. The commit
is Cc'ed to stable so we can expect 6.16.y will be fixed soon as well.
--
Xi Ruoyao <xry111@xry111.site>
prev parent reply other threads:[~2025-10-25 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 9:10 [PATCH V2] LoongArch: Align ACPI structures if ARCH_STRICT_ALIGN enabled Huacai Chen
2025-09-11 0:59 ` kernel test robot
2025-09-11 8:41 ` Huacai Chen
2025-09-20 23:48 ` Nathan Chancellor
2025-09-21 1:07 ` Huacai Chen
2025-09-26 14:31 ` Guenter Roeck
2025-09-26 17:15 ` Xi Ruoyao
2025-09-26 18:27 ` Guenter Roeck
2025-10-25 13:02 ` Xi Ruoyao [this message]
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=274fe4e6ff05401bc43d952efe69908fe052d875.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=guoren@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lixuefeng@loongson.cn \
--cc=loongarch@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=stable@vger.kernel.org \
--cc=zhoubinbin@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