From: Linus Torvalds <torvalds@linux-foundation.org>
To: Frank Scheiner <frank.scheiner@web.de>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Tomáš Glozar" <tglozar@gmail.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux-Arch <linux-arch@vger.kernel.org>,
"Ard Biesheuvel" <ardb@kernel.org>
Subject: Re: [GIT PULL] asm-generic updates for v6.7
Date: Thu, 2 Nov 2023 07:28:45 -1000 [thread overview]
Message-ID: <CAHk-=whFLZ67ffzt1juryCYcYz6eL_XjQF8WucDzwUR5H65+rA@mail.gmail.com> (raw)
In-Reply-To: <8ff191a0-41fa-4f36-86e8-3d32ff3fe75c@web.de>
On Thu, 2 Nov 2023 at 00:24, Frank Scheiner <frank.scheiner@web.de> wrote:
>
> so the ia64 removal happened despite the efforts - not only from us - to
> keep it alive in Linux. That is a - sad - fact now.
Well, I'd have personally been willing to resurrect it, but I was told
several times that other projects were basically just waiting for the
kernel support to die.
Has the itanium situation really changed?
The thing is, nobody doing new kernel code wants to deal with itanium,
so relegating it to the same situation that i386 support was ("it
still works in old kernels") doesn't seem to be a huge issue for the
people who actually want to use those machines.
That said, I'd be willing to resurrect itanium support, even though I
personally despise the architecture with a passion for being
fundamentally based on faulty design premises, and an implementation
based on politics rather than good technical design.
But only if it turns out to actually have some long-term active
interest (ie I'd compare it to the situation with m68k etc - clearly
dead architectures that we still support despite them being not
relevant - because some people care and they don't cause pain).
So I'd be willing to come back to the "can we resurrect it"
discussion, but not immediately - more along the lines of a "look,
we've been maintaining it out of tree for a year, the other
infrastructure is still alive, there is no impact on the rest of the
kernel, can we please try again"?
Linus
next prev parent reply other threads:[~2023-11-02 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 23:50 [GIT PULL] asm-generic updates for v6.7 Arnd Bergmann
2023-11-02 2:51 ` pr-tracker-bot
2023-11-02 10:24 ` Frank Scheiner
2023-11-02 17:28 ` Linus Torvalds [this message]
2023-11-02 17:36 ` John Paul Adrian Glaubitz
2023-11-02 19:15 ` Tomáš Glozar
2023-11-03 17:40 ` Frank Scheiner
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='CAHk-=whFLZ67ffzt1juryCYcYz6eL_XjQF8WucDzwUR5H65+rA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=frank.scheiner@web.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglozar@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).