linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Ard Biesheuvel <ardb@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>, Arnd Bergmann <arnd@arndb.de>,
	Jessica Clarke <jrtc27@jrtc27.com>,
	Matthew Wilcox <willy@infradead.org>,
	Marc Zyngier <maz@kernel.org>, Guenter Roeck <linux@roeck-us.net>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>
Subject: Re: [RFC PATCH 0/5] Retire IA64/Itanium support
Date: Thu, 16 Feb 2023 07:04:53 +0200	[thread overview]
Message-ID: <Y+25dZiA+xnZRgVX@kernel.org> (raw)
In-Reply-To: <CAHk-=wj9RkLN+GpYcFmsd8tze6zYL7MMkNpvdKbETQnqYm+Hwg@mail.gmail.com>

Hi Linus,

On Wed, Feb 15, 2023 at 12:08:28PM -0800, Linus Torvalds wrote:
> On Wed, Feb 15, 2023 at 11:43 AM Luck, Tony <tony.luck@intel.com> wrote:
> >
> > Maybe you don't see others pain?  I added Al Viro ... perhaps
> > he'll replay some of his thoughts from trying to make signals
> > and other stuff work correctly on ia64.
> 
> Well, as long as it's ia64-specific, I'll just go "hey, it was Al's
> choice to look at that code".
> 
> IOW, I'm more worried about "ia64 makes it a pain to make _generic_ changes".
> 
> IOW, doing something like this:
> 
>     git log -p --no-merges --since=1.year arch/ia64/
> 
> to see what kind of pain ia64 parts of patches have caused, about a
> third of them are that "look, somebody cared about ia64 explicitly".
 
I remember that when I was doing cleanups of mm initialization, ia64
required special care several times.

> That said, it's entirely possible I've missed some particular painpoint.

The largest painpoint IMO is absence of any ability to test ia64 except
sending patches to Adrian in a hope he has time to give them a whirl.
 
>                   Linus

-- 
Sincerely yours,
Mike.

  parent reply	other threads:[~2023-02-16  5:05 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 [this message]
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
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=Y+25dZiA+xnZRgVX@kernel.org \
    --to=rppt@kernel.org \
    --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=viro@zeniv.linux.org.uk \
    --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).