linux-ia64.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	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, 02 Nov 2023 18:36:39 +0100	[thread overview]
Message-ID: <396c3aebd6a382aa5a9cbf333f93d876467e12e9.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <CAHk-=whFLZ67ffzt1juryCYcYz6eL_XjQF8WucDzwUR5H65+rA@mail.gmail.com>

Hi Linus!

On Thu, 2023-11-02 at 07:28 -1000, Linus Torvalds wrote:
> 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.

This made my day. :-)

> 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).

Fully agreed.

> 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"?

I think this is a very reasonable approach. If the keeping the architecture
alive is sustainable, it should be possible to do that out of tree for a
given period of time.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2023-11-02 17:37 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 [this message]
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=396c3aebd6a382aa5a9cbf333f93d876467e12e9.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --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 \
    --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).