All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [crosspost] dropping support for ia64
Date: Mon, 22 May 2023 16:56:46 +0000	[thread overview]
Message-ID: <2023052202-stumble-debtless-8613@gregkh> (raw)
In-Reply-To: <CAMj1kXFCMh_578jniKpUtx_j8ByHnt=s7S+yQ+vGbKt9ud7+kQ@mail.gmail.com>

On Mon, May 22, 2023 at 09:46:57AM +0200, Ard Biesheuvel wrote:
> On Mon, 22 May 2023 at 09:39, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Mon, May 22, 2023 at 09:08:35AM +0200, Ard Biesheuvel wrote:
> > > (cc Greg as stable maintainer)
> > >
> > > On Sat, 20 May 2023 at 21:23, John Paul Adrian Glaubitz
> > > <glaubitz@physik.fu-berlin.de> wrote:
> > > >
> > > ...
> > > >
> > > > I have been thinking about this discussion for a while now and my suggestion
> > > > would be to drop ia64 support from the kernel, GRUB and gcc/binutils/glibc in
> > > > this order:
> > > >
> > > > - Kernel: After the next LTS release
> > > > - GRUB: After the 2.12 release
> > > > - gcc/binutils/glibc: After support was dropped from the kernel
> > > >
> > > > This way anyone still using ia64 will be able to use it with a supported codebase
> > > > for an extended time and upstream projects have target releases for which they
> > > > can plan the removal.
> > > >
> > >
> > > Yeah, I think this is reasonable. Having a clear agreement on where
> > > the support ends helps both the remaining users and the developers
> > > eager to move on.
> > >
> > > My only question is how we would land fixes for ia64 into this Linux
> > > LTS release if there is no upstream any longer to draw from.
> > >
> > > Greg, could you comment on this?
> >
> > That would imply that people actually used that arch and code, so why
> > would it have been removed from Linus's tree?
> >
> 
> As far as we have been able to establish, the only people that use
> this arch and code are people that would hate to see it go, but don't
> actually use it for anything other than checking whether it still
> boots, and don't have the skills or bandwidth to step up and maintain
> it upstream.

Great, then let's drop it today, there is no need to wait until the end
of the year as nothing is going to change then.

thanks,

greg k-h

  parent reply	other threads:[~2023-05-22 16:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 15:57 [crosspost] dropping support for ia64 Ard Biesheuvel
2023-05-12 18:50 ` Jesse Dougherty
2023-05-12 19:24 ` Luck, Tony
2023-05-12 20:02 ` Ard Biesheuvel
2023-05-17 18:38 ` Frank Scheiner
2023-05-17 19:39 ` Florian Weimer
2023-05-17 21:41 ` Ard Biesheuvel
2023-05-17 21:47 ` matoro
2023-05-19 20:17 ` Frank Scheiner
2023-05-19 20:17 ` Frank Scheiner
2023-05-19 20:56 ` matoro
2023-05-20 16:48 ` Florian Weimer
2023-05-20 19:22 ` John Paul Adrian Glaubitz
2023-05-20 19:27 ` John Paul Adrian Glaubitz
2023-05-20 19:49 ` John Paul Adrian Glaubitz
2023-05-22  7:08 ` Ard Biesheuvel
2023-05-22  7:39 ` Greg Kroah-Hartman
2023-05-22  7:46 ` Ard Biesheuvel
2023-05-22 16:56 ` Greg Kroah-Hartman [this message]
2023-05-22 17:27 ` Luck, Tony
2023-05-22 17:38 ` Greg Kroah-Hartman

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=2023052202-stumble-debtless-8613@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.