linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Arnd Bergmann <arnd@arndb.de>, Tony Luck <tony.luck@intel.com>,
	Jessica Clarke <jrtc27@jrtc27.com>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Matthew Wilcox <willy@infradead.org>,
	Marc Zyngier <maz@kernel.org>, Guenter Roeck <linux@roeck-us.net>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-ia64@vger.kernel.org
Subject: Re: [RFC PATCH 0/5] Retire IA64/Itanium support
Date: Fri, 17 Mar 2023 23:55:59 +0100	[thread overview]
Message-ID: <87y1nvng1s.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20230215100008.2565237-1-ardb@kernel.org> (Ard Biesheuvel's message of "Wed, 15 Feb 2023 11:00:03 +0100")

* Ard Biesheuvel:

> The IA64 port of Linux has no maintainer, and according to a report from
> its only remaining user [0], it has been broken for a month and nobody
> cares.
>
> Given that keeping a complex but unused architecture alive uses up
> valuable developer bandwidth, let's just get rid of it.
>
> This supersedes my patch proposing to mark it as 'dead', which received
> no replies from anyone that wants to keep it alive. [1]

Is this still going ahead?

In userspace, ia64 is of course full of special cases, too, so many of
us really want to see it gone, but we can't really start the removal
process while there is still kernel support.

  parent reply	other threads:[~2023-03-17 23:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15 10:00 [RFC PATCH 0/5] Retire IA64/Itanium support Ard Biesheuvel
2023-02-15 10:00 ` [RFC PATCH 1/5] arch: Remove Itanium (IA-64) architecture Ard Biesheuvel
2023-02-15 16:55   ` Guenter Roeck
2023-02-15 16:58   ` Guenter Roeck
2023-02-15 16:59     ` Ard Biesheuvel
2023-02-15 10:00 ` [RFC PATCH 2/5] kernel: Drop IA64 support from sig_fault handlers Ard Biesheuvel
2023-02-15 10:19   ` Arnd Bergmann
2023-02-15 11:13     ` Arnd Bergmann
2023-02-15 11:22       ` Ard Biesheuvel
2023-02-15 12:46         ` Arnd Bergmann
2023-02-15 10:00 ` [RFC PATCH 3/5] Documentation: Drop IA64 from feature descriptions Ard Biesheuvel
2023-02-15 10:00 ` [RFC PATCH 4/5] lib/raid6: Drop IA64 support Ard Biesheuvel
2023-02-15 10:00 ` [RFC PATCH 5/5] Documentation: Drop or replace remaining mentions of IA64 Ard Biesheuvel
2023-02-15 10:17 ` [RFC PATCH 0/5] Retire IA64/Itanium support John Paul Adrian Glaubitz
2023-02-15 19:30   ` Linus Torvalds
2023-02-15 19:42     ` Luck, Tony
2023-02-15 20:08       ` Linus Torvalds
2023-02-15 23:13         ` John Paul Adrian Glaubitz
2023-02-22 21:52           ` matoro
2023-02-16  5:04         ` Mike Rapoport
2023-02-15 23:09     ` John Paul Adrian Glaubitz
2023-02-15 16:50 ` Palmer Dabbelt
2023-02-15 17:00   ` Ard Biesheuvel
2023-02-15 18:20     ` Palmer Dabbelt
2023-03-17 22:55 ` Florian Weimer [this message]
2023-05-12 14:45   ` Ard Biesheuvel
2023-05-12 14:58     ` Florian Weimer

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=87y1nvng1s.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=corbet@lwn.net \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=jrtc27@jrtc27.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=maz@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@infradead.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 NNTP newsgroup(s).