All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [crosspost] dropping support for ia64
Date: Mon, 22 May 2023 17:27:23 +0000	[thread overview]
Message-ID: <SJ1PR11MB60833AF98E6E9D3CD89AB393FC439@SJ1PR11MB6083.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAMj1kXFCMh_578jniKpUtx_j8ByHnt=s7S+yQ+vGbKt9ud7+kQ@mail.gmail.com>

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

I think this also puts the existing stable and LTS trees in some interesting
state. After arch/ia64 is removed, there may be some tree-wide change
that gets backported to stable & LTS. That may break arch/ia64 in those
trees (e.g. because arguments to some common function are changed).

Maybe just deal with that if it happens ... and if anyone notices ... are there
automated builds and boot test for ia64 in those trees?

-Tony

  parent reply	other threads:[~2023-05-22 17:27 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
2023-05-22 17:27 ` Luck, Tony [this message]
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=SJ1PR11MB60833AF98E6E9D3CD89AB393FC439@SJ1PR11MB6083.namprd11.prod.outlook.com \
    --to=tony.luck@intel.com \
    --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.