All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [crosspost] dropping support for ia64
Date: Fri, 12 May 2023 20:02:32 +0000	[thread overview]
Message-ID: <CAMj1kXFBqkFO4hN=40Zv46r3xaym9oPMRMN+e_7AwuhL0vK4Vg@mail.gmail.com> (raw)
In-Reply-To: <CAMj1kXFCMh_578jniKpUtx_j8ByHnt=s7S+yQ+vGbKt9ud7+kQ@mail.gmail.com>

On Fri, 12 May 2023 at 20:50, Jesse Dougherty <Jesse@cypress-tech.com> wrote:
>
> I'm a little bias because my company is a re-sellers of the HP Itanium
> ia64 hardware (RX & ZX boxes), as well as PA-RISC. For that reason, I
> would hate to see it fade away in any sector. The ia64 platform is still
> widely used with HP-UX Unix and Open VMS users worldwide. This hardware
> is embedded in most every data center and large and medium companies
> that have been around since the 80s/90s, its probably the oldest box
> they have in there but its the one thats in the corner running for 20
> years, long before most people started working there. PA-RICS is also
> massively intertwined into the US military as well as foreign
> military's, they did that in the early 2000's and they are stuck with it..
>
> I could go on but me as a hardware guy, I'm on team ia64 :-)
>

Thanks for the data point. Gwtting your angle as someone who supports
actual users is rather useful.

So how many of your customers would be adversely impacted by the lack
of an upgrade path to, say, Linux kernels beyond v6.3 or GRUB versions
beyond today's 2.06?

  parent reply	other threads:[~2023-05-12 20:02 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 [this message]
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
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='CAMj1kXFBqkFO4hN=40Zv46r3xaym9oPMRMN+e_7AwuhL0vK4Vg@mail.gmail.com' \
    --to=ardb@kernel.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.