From: Greg KH <gregkh@linuxfoundation.org>
To: WangYuli <wangyuli@uniontech.com>
Cc: ardb@kernel.org, chenhuacai@kernel.org, chenhuacai@loongson.cn,
kernel@xen0n.name, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
masahiroy@kernel.org, nathan@kernel.org, ndesaulniers@google.com,
nicolas@fjasle.eu, sashal@kernel.org, stable@vger.kernel.org
Subject: Re: Re: [PATCH 6.1&6.6 0/3] kbuild: Avoid weak external linkage where possible
Date: Thu, 6 Feb 2025 11:03:30 +0100 [thread overview]
Message-ID: <2025020611-olive-gluten-fa45@gregkh> (raw)
In-Reply-To: <F6E14B0130692444+20250206083705.63378-1-wangyuli@uniontech.com>
On Thu, Feb 06, 2025 at 04:37:02PM +0800, WangYuli wrote:
> Hi, Greg,
>
> It's rather unfortunate that currently, almost all Linux distributions
> supporting LoongArch are using LTS kernels version v6.6 or older, such as
> openEuler and deepin. [1][2]
>
> If this bugfix isn't merged into linux-stable, then every single distro
> kernel team will have to waste time fixing the same darn bug over and
> over, even though it's already fixed in later kernels.
>
> This would really make LTS look like it's failing to serve its intended
> purpose. And I'm sure all of us do not want to see something so terrible
> happen.
LTS is here to ensure that the original release of these branches, keeps
working for that branch. Adding support for newer toolchains sometimes
happens, but is not a requirement or a normal thing to do as that really
isn't a "regression", right?
Most of the time, fixing things up for newer compilers is simple.
Sometimes it is not simple. The "not simple" ones we usually just do
not backport as that causes extra work for everyone over time.
As for the distros like openEuler, and deepin, they are free to add
these patches there, on top of their other non-LTS patches, right?
thanks,
greg k-h
next prev parent reply other threads:[~2025-02-06 14:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 8:58 [PATCH 6.1&6.6 0/3] kbuild: Avoid weak external linkage where possible Huacai Chen
2024-12-06 8:58 ` [PATCH 6.1&6.6 1/3] kallsyms: Avoid weak references for kallsyms symbols Huacai Chen
2024-12-06 8:58 ` [PATCH 6.1&6.6 2/3] vmlinux: Avoid weak reference to notes section Huacai Chen
2024-12-06 8:58 ` [PATCH 6.1&6.6 3/3] btf: Avoid weak external references Huacai Chen
2024-12-06 13:04 ` [PATCH 6.1&6.6 0/3] kbuild: Avoid weak external linkage where possible Greg Kroah-Hartman
2024-12-07 9:21 ` Huacai Chen
2024-12-07 9:32 ` Greg Kroah-Hartman
2024-12-07 10:46 ` Xi Ruoyao
2024-12-09 8:31 ` Ard Biesheuvel
2024-12-09 10:01 ` Xi Ruoyao
2025-02-06 8:37 ` WangYuli
2025-02-06 9:31 ` Ard Biesheuvel
2025-02-06 10:03 ` Greg KH [this message]
2025-09-05 6:49 ` Ming Wang
2025-09-05 7:09 ` Greg KH
2025-09-05 8:29 ` Ming Wang
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=2025020611-olive-gluten-fa45@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ardb@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=kernel@xen0n.name \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wangyuli@uniontech.com \
/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