linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: linux-kernel@vger.kernel.org, corbet@lwn.net,
	Arnd Bergmann <arnd@arndb.de>,
	tony.luck@intel.com, jrtc27@jrtc27.com,
	glaubitz@physik.fu-berlin.de, willy@infradead.org,
	Marc Zyngier <maz@kernel.org>,
	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: Wed, 15 Feb 2023 18:00:28 +0100	[thread overview]
Message-ID: <CAMj1kXFmZYmrZB7QyLCu3rpkChat=PVqPHsOi+HuWRj-FZ2S-g@mail.gmail.com> (raw)
In-Reply-To: <mhng-37f3f56f-70a4-4800-8685-e9a4c5922ce5@palmer-ri-x1c9>

On Wed, 15 Feb 2023 at 17:50, Palmer Dabbelt <palmer@dabbelt.com> wrote:
>
> On Wed, 15 Feb 2023 02:00:03 PST (-0800), ardb@kernel.org wrote:
> > 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]
> >
> > [0] https://www.spinics.net/lists/linux-ia64/msg21926.html
> > [1] https://lore.kernel.org/all/20230128122904.1345120-1-ardb@kernel.org/
> >
> > Cc: Jonathan Corbet <corbet@lwn.net>
> > Cc: Arnd Bergmann <arnd@arndb.de>
> > Cc: Tony Luck <tony.luck@intel.com>
> > Cc: Jessica Clarke <jrtc27@jrtc27.com>
> > Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
> > Cc: Matthew Wilcox <willy@infradead.org>
> > Cc: Marc Zyngier <maz@kernel.org>
> > Cc: Guenter Roeck <linux@roeck-us.net>
> > Cc: Linus Torvalds <torvalds@linux-foundation.org>
> > Cc: linux-ia64@vger.kernel.org
> >
> > Ard Biesheuvel (5):
> >   arch: Remove Itanium (IA-64) architecture
> >   kernel: Drop IA64 support from sig_fault handlers
> >   Documentation: Drop IA64 from feature descriptions
> >   lib/raid6: Drop IA64 support
> >   Documentation: Drop or replace remaining mentions of IA64
>
> Not sure if I'm missing it in the diff, but it looks like there's also a
> bunch of "#ifdef __ia64__" and "#ifdef __IA64__" type code spread
> throughout the kernel.  I didn't look at the actual diff, but it's in
> files that aren't showing up in the diffstat.
>

Thanks for taking a look. It seems I indeed missed a couple.

> Just "git grep -i __ia64__" lists a bunch.  I didn't look at all of
> them, but at least spot checking include/acpi/actypes.h looks like it's
> a real Itanium workaround.  If the arch goes, it's probbaly worth
> removing those too?
>

The ACPI code is synced with another project, so I didn't touch it.
Same goes for some other header files where IA-64 is referenced, e.g.,
in the PE/COFF header stuff.

> There's also some mentions of "Itanium" in Documentation outside that
> don't look like they got caught here.  Not sure if they'd be worth
> getting rid of, though as they could still be useful examples.  The
> blurb in Documentation/memory-barriers.txt looks pretty port-specific,
> though.
>

Yeah, I don't think it is necessary to rewrite history soviet-style,
so some remaining references are fine IMHO.

  reply	other threads:[~2023-02-15 17:00 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 [this message]
2023-02-15 18:20     ` Palmer Dabbelt
2023-03-17 22:55 ` Florian Weimer
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='CAMj1kXFmZYmrZB7QyLCu3rpkChat=PVqPHsOi+HuWRj-FZ2S-g@mail.gmail.com' \
    --to=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=palmer@dabbelt.com \
    --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).