From: Frank Scheiner <frank.scheiner@web.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
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: Fri, 3 Nov 2023 18:40:19 +0100 [thread overview]
Message-ID: <6e745433-d7eb-45df-b607-5589f1e04e86@web.de> (raw)
In-Reply-To: <CAHk-=whFLZ67ffzt1juryCYcYz6eL_XjQF8WucDzwUR5H65+rA@mail.gmail.com>
On 02.11.23 18:28, Linus Torvalds wrote:
> 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?
Well, we definitely made some progress in this regard. But as you wrote,
this was not a pressing issue as long as ia64 stayed in the kernel.
Which is why I wanted to concentrate on kernel support first and
foremost. My thinking was that a working architecture wouldn't be
dropped*. And with kernel support saved, we could have gone full steam
ahead into the other projects.
Well, we did proceed with tackling the problems in the other projects
anyhow from the start, but now the situation is a little different.
*)
https://lore.kernel.org/linux-ia64/CAHk-=wjEmZ19T4XpVb0_Hacm53xJG_w5ygcuorwC0xBoT-myUA@mail.gmail.com/
> 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"?
That is really something.
We'll see where this goes. I always hope for the best. (-:
If you feel like checking on our status, you know where to look (see my
email to you from 2023-09-23).
Cheers,
Frank
prev parent reply other threads:[~2023-11-03 17:40 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
2023-11-02 17:36 ` John Paul Adrian Glaubitz
2023-11-02 19:15 ` Tomáš Glozar
2023-11-03 17:40 ` Frank Scheiner [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=6e745433-d7eb-45df-b607-5589f1e04e86@web.de \
--to=frank.scheiner@web.de \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglozar@gmail.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).