From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
"Bill Wendling" <morbo@google.com>,
"Borislav Petkov" <bp@alien8.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Justin Stitt" <justinstitt@google.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Neal Gompa" <neal@gompa.dev>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Richard Purdie" <richard.purdie@linuxfoundation.org>,
"Sam James" <sam@gentoo.org>, "Shuah Khan" <shuah@kernel.org>,
"Thomas Gleixner" <tglx@kernel.org>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Tomas Glozar" <tglozar@kernel.org>, "Willy Tarreau" <w@1wt.eu>,
x86@kernel.org, "Arnd Bergmann" <arnd@arndb.de>
Subject: Re: [PATCH v3 2/2] x86: Start removing X86_X32_ABI
Date: Thu, 13 Aug 2026 15:47:20 +0200 [thread overview]
Message-ID: <8af1dc8eba9c8a01dd33deda02e9c5d47adf4b11.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <20260813134121.2vaFywr3@linutronix.de>
Hi Sebastian,
On Thu, 2026-08-13 at 15:41 +0200, Sebastian Andrzej Siewior wrote:
> On 2026-08-13 14:24:39 [+0200], John Paul Adrian Glaubitz wrote:
> > Hi Sebastian,
> Hi Adrian,
>
> > > The idea is to revert the (two) commit(s).
> >
> > But that imply that anyone concerned would have to respond in a timely manner
> > which is not really something I would expect.
>
> What do you mean by respond in a timely manner?
Well, the problem of many kernel maintainers is that they somehow assume that 99%
of the Linux users are present on the Linux kernel mailing list and reading what's
happening there.
Then a kernel developers send a patch introducing a major breaking change, ask for
feedback and then just implement the change because they didn't get any feedback.
However, most users are not reading the LKML, so introducing such breaking changes
in steps hoping for feedback will not work.
My recommendation is therefore to keep everything in a working state until the next
LTS release, then drop everything at once. This way users know that they can stick
for the latest LTS release for the time being to continue to use such a major feature.
> > My suggestion would be to leave the complete x32 support fully intact until
> > the next LTS release so that anyone using that LTS release will know that x32
> > will be fully working.
>
> Given the media covered it well, it might work.
Most users probably don't even read the media coverage and only realize that a feature
is gone when they try to upgrade their machines and realize the feature has suddenly
vanished.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
prev parent reply other threads:[~2026-08-13 13:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 11:04 [PATCH v3 0/2] " Sebastian Andrzej Siewior
2026-08-13 11:04 ` [PATCH v3 1/2] selftests/nolibc: remove the x32 testcase Sebastian Andrzej Siewior
2026-08-13 11:04 ` [PATCH v3 2/2] x86: Start removing X86_X32_ABI Sebastian Andrzej Siewior
2026-08-13 11:07 ` John Paul Adrian Glaubitz
2026-08-13 12:11 ` Sebastian Andrzej Siewior
2026-08-13 12:24 ` John Paul Adrian Glaubitz
2026-08-13 13:41 ` Sebastian Andrzej Siewior
2026-08-13 13:47 ` John Paul Adrian Glaubitz [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=8af1dc8eba9c8a01dd33deda02e9c5d47adf4b11.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=macro@orcam.me.uk \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=neal@gompa.dev \
--cc=richard.purdie@linuxfoundation.org \
--cc=sam@gentoo.org \
--cc=shuah@kernel.org \
--cc=tglozar@kernel.org \
--cc=tglx@kernel.org \
--cc=w@1wt.eu \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®