From: "Arnd Bergmann" <arnd@arndb.de>
To: Ard Biesheuvel <ardb@kernel.org>, linux-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>, 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 2/5] kernel: Drop IA64 support from sig_fault handlers
Date: Wed, 15 Feb 2023 10:19:18 +0000 [thread overview]
Message-ID: <ea12dd12-db17-44a8-8c29-6b0a129f355d@app.fastmail.com> (raw)
In-Reply-To: <20230215100008.2565237-3-ardb@kernel.org>
On Wed, Feb 15, 2023, at 11:00, Ard Biesheuvel wrote:
> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> ---
> include/linux/sched/signal.h | 17 ++++---------
> kernel/signal.c | 25 ++++----------------
> 2 files changed, 9 insertions(+), 33 deletions(-)
The patch looks good, but I'd suggest adding a oneline description
referencing that ia64 as a whole is removed.
I see that you created a couple of patches looking for __ia64__
but not CONFIG_IA64. If we get consensus on patch 1, we should
do that as well, let me know if you you want to add those or
would like me to help here.
I can probably do the same recursive check for removed Kconfig
options that I used for finding dead code after the boardfile
removal.
Arnd
next prev parent reply other threads:[~2023-02-15 10:19 UTC|newest]
Thread overview: 29+ 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 2/5] kernel: Drop IA64 support from sig_fault handlers Ard Biesheuvel
2023-02-15 10:19 ` Arnd Bergmann [this message]
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
2023-02-15 23:09 ` John Paul Adrian Glaubitz
2023-02-15 16:50 ` Palmer Dabbelt
2023-02-15 16:59 ` Ard Biesheuvel
2023-02-15 18:20 ` Palmer Dabbelt
[not found] ` <20230215100008.2565237-2-ardb@kernel.org>
2023-02-15 16:58 ` [RFC PATCH 1/5] arch: Remove Itanium (IA-64) architecture Guenter Roeck
2023-02-15 16:59 ` Ard Biesheuvel
2023-02-16 17:42 ` [RFC PATCH 0/5] Retire IA64/Itanium support 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-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=ea12dd12-db17-44a8-8c29-6b0a129f355d@app.fastmail.com \
--to=arnd@arndb.de \
--cc=ardb@kernel.org \
--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: 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).