From: Florian Weimer <fw@deneb.enyo.de> To: Ard Biesheuvel <ardb@kernel.org> Cc: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>, Arnd Bergmann <arnd@arndb.de>, Tony Luck <tony.luck@intel.com>, Jessica Clarke <jrtc27@jrtc27.com>, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>, Matthew Wilcox <willy@infradead.org>, Marc Zyngier <maz@kernel.org>, Guenter Roeck <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: Fri, 12 May 2023 16:58:31 +0200 [thread overview] Message-ID: <873541ha08.fsf@mid.deneb.enyo.de> (raw) In-Reply-To: <CAMj1kXGXCFFQQObtkGje=Hym0GuEgR3h85MX8d1_hBb=b3Fxdg@mail.gmail.com> (Ard Biesheuvel's message of "Fri, 12 May 2023 16:45:55 +0200") * Ard Biesheuvel: > I brought this up again [0] in the context of GRUB (which has similar > issues related to EFI the the kernel has) and Adrian suggested to > raise this discussion more widely, perhaps on the distributions > mailing list, among other places. > > Do you have any recommendations for a venue where we might find the > right mix of people who can drive this to a conclusion one way or the > other? > [0] https://lists.gnu.org/archive/html/grub-devel/2023-05/msg00068.html I think Adrian's list of lists to concat looks reasonable.
WARNING: multiple messages have this Message-ID (diff)
From: Florian Weimer <fw@deneb.enyo.de> To: Ard Biesheuvel <ardb@kernel.org> Cc: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>, Arnd Bergmann <arnd@arndb.de>, Tony Luck <tony.luck@intel.com>, Jessica Clarke <jrtc27@jrtc27.com>, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>, Matthew Wilcox <willy@infradead.org>, Marc Zyngier <maz@kernel.org>, Guenter Roeck <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: Fri, 12 May 2023 14:58:31 +0000 [thread overview] Message-ID: <873541ha08.fsf@mid.deneb.enyo.de> (raw) In-Reply-To: <CAMj1kXGXCFFQQObtkGje=Hym0GuEgR3h85MX8d1_hBb=b3Fxdg@mail.gmail.com> (Ard Biesheuvel's message of "Fri, 12 May 2023 16:45:55 +0200") * Ard Biesheuvel: > I brought this up again [0] in the context of GRUB (which has similar > issues related to EFI the the kernel has) and Adrian suggested to > raise this discussion more widely, perhaps on the distributions > mailing list, among other places. > > Do you have any recommendations for a venue where we might find the > right mix of people who can drive this to a conclusion one way or the > other? > [0] https://lists.gnu.org/archive/html/grub-devel/2023-05/msg00068.html I think Adrian's list of lists to concat looks reasonable.
next prev parent reply other threads:[~2023-05-12 15:05 UTC|newest] Thread overview: 56+ 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 ` 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:58 ` Guenter Roeck 2023-02-15 16:59 ` Ard Biesheuvel 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:00 ` Ard Biesheuvel 2023-02-15 10:19 ` Arnd Bergmann 2023-02-15 10:19 ` Arnd Bergmann 2023-02-15 11:13 ` Arnd Bergmann 2023-02-15 11:13 ` Arnd Bergmann 2023-02-15 11:22 ` Ard Biesheuvel 2023-02-15 11:22 ` Ard Biesheuvel 2023-02-15 12:46 ` Arnd Bergmann 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 ` Ard Biesheuvel 2023-02-15 10:00 ` [RFC PATCH 4/5] lib/raid6: Drop IA64 support Ard Biesheuvel 2023-02-15 10:00 ` 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:00 ` Ard Biesheuvel 2023-02-15 10:17 ` [RFC PATCH 0/5] Retire IA64/Itanium support John Paul Adrian Glaubitz 2023-02-15 10:17 ` John Paul Adrian Glaubitz 2023-02-15 19:30 ` Linus Torvalds 2023-02-15 19:30 ` Linus Torvalds 2023-02-15 19:42 ` Luck, Tony 2023-02-15 19:42 ` Luck, Tony 2023-02-15 20:08 ` Linus Torvalds 2023-02-15 20:08 ` Linus Torvalds 2023-02-15 23:13 ` John Paul Adrian Glaubitz 2023-02-15 23:13 ` John Paul Adrian Glaubitz 2023-02-22 21:52 ` matoro 2023-02-22 21:52 ` matoro 2023-02-16 5:04 ` Mike Rapoport 2023-02-16 5:04 ` Mike Rapoport 2023-02-15 23:09 ` John Paul Adrian Glaubitz 2023-02-15 23:09 ` John Paul Adrian Glaubitz 2023-02-15 16:50 ` Palmer Dabbelt 2023-02-15 16:50 ` Palmer Dabbelt 2023-02-15 16:59 ` Ard Biesheuvel 2023-02-15 17:00 ` Ard Biesheuvel 2023-02-15 18:20 ` Palmer Dabbelt 2023-02-15 18:20 ` Palmer Dabbelt 2023-02-16 17:42 ` Pedro Miguel Justo 2023-02-16 18:32 ` Ard Biesheuvel 2023-02-16 19:17 ` Guenter Roeck 2023-02-16 19:34 ` Matthew Wilcox 2023-03-17 22:55 ` Florian Weimer 2023-03-17 22:55 ` Florian Weimer 2023-05-12 14:45 ` Ard Biesheuvel 2023-05-12 14:45 ` Ard Biesheuvel 2023-05-12 14:58 ` Florian Weimer [this message] 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=873541ha08.fsf@mid.deneb.enyo.de \ --to=fw@deneb.enyo.de \ --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=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: linkBe 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.