From: Huacai Chen <chenhuacai@kernel.org>
To: Xi Ruoyao <xry111@xry111.site>
Cc: "WANG Xuerui" <kernel@xen0n.name>,
"Thomas Weißschuh" <linux@weissschuh.net>,
loongarch@lists.linux.dev, "Zixing Liu" <liushuyu@aosc.io>,
"Mingcong Bai" <jeffbai@aosc.io>, "Arnd Bergmann" <arnd@arndb.de>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"George Guo" <dongtai.guo@linux.dev>,
linux-kernel@vger.kernel.org
Subject: Re: Ping: [PATCH v2] LoongArch: detect and disable sc.q if erratic
Date: Wed, 29 Apr 2026 10:13:22 +0800 [thread overview]
Message-ID: <CAAhV-H5z0EHrC5i_VvGBpX4v5tHVmkeHd8Z=zUMrKzvX0w3+4Q@mail.gmail.com> (raw)
In-Reply-To: <f71d329c66c873cf756623037d1e5806a9c94898.camel@xry111.site>
On Tue, Apr 28, 2026 at 11:49 PM Xi Ruoyao <xry111@xry111.site> wrote:
>
> On Mon, 2026-04-27 at 16:43 +0800, Huacai Chen wrote:
> > Hi, Ruoyao,
> >
> > On Mon, Apr 27, 2026 at 10:17 AM Xi Ruoyao <xry111@xry111.site> wrote:
> > >
> > > Ping.
> > Can we keep this as an out-of-tree patch? It's a bit ugly and I think
> > the corrct way is update firmware.
>
> We can try harder urging the vendors to release the firmware update
> (there are other firmware bugs those the kernel cannot deal with anyway)
> but in many cases the users just complain "hey your distro doesn't boot"
> to the distro maintainers. And some rogue ODM/OEM tend to ignore any
> reports relayed by the distro maintainers unless the distro pays some
> thousands of dollar.
I know, but distro kernels usually carry out-of-tree patches, this is
not the only one, right?
Huacai
>
> Thus IMO it's better to make the system at least bootable with a message
> (the pr_warn_once line in the patch) to clearly indicate the users that
> they need a firmware update, and the vendors may become motivated a
> little with more users complaining directly.
> >
>
> --
> Xi Ruoyao <xry111@xry111.site>
next prev parent reply other threads:[~2026-04-29 2:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 12:19 [PATCH v2] LoongArch: detect and disable sc.q if erratic Xi Ruoyao
2026-04-27 2:17 ` Ping: " Xi Ruoyao
2026-04-27 8:43 ` Huacai Chen
2026-04-28 15:49 ` Xi Ruoyao
2026-04-29 2:13 ` Huacai Chen [this message]
2026-04-28 18:47 ` Yao Zi
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='CAAhV-H5z0EHrC5i_VvGBpX4v5tHVmkeHd8Z=zUMrKzvX0w3+4Q@mail.gmail.com' \
--to=chenhuacai@kernel.org \
--cc=arnd@arndb.de \
--cc=dongtai.guo@linux.dev \
--cc=jeffbai@aosc.io \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=liushuyu@aosc.io \
--cc=loongarch@lists.linux.dev \
--cc=xry111@xry111.site \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).