From: "Arnd Bergmann" <arnd@arndb.de>
To: Guenter Roeck <linux@roeck-us.net>, Ard Biesheuvel <ardb@kernel.org>
Cc: linux-kernel@vger.kernel.org, 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>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-ia64@vger.kernel.org
Subject: Re: [RFC PATCH] MAINTAINERS: Mark Itanium/IA64 as 'dead'
Date: Wed, 15 Feb 2023 15:36:23 +0000 [thread overview]
Message-ID: <33201710-a18b-44a6-8e09-364f4a9ca5e5@app.fastmail.com> (raw)
In-Reply-To: <20230215151547.GA3766362@roeck-us.net>
On Wed, Feb 15, 2023, at 16:15, Guenter Roeck wrote:
> On Sat, Jan 28, 2023 at 01:29:04PM +0100, Ard Biesheuvel wrote:
>> Create a new status 'dead' which conveys that a subsystem is
>> unmaintained and scheduled for removal, and developers are free to
>> behave as if it's already gone. Also, automated build tests should
>> ignore such subsystems, or at least notify only those who are known to
>> have an interest in the subsystem in particular.
>>
>> Given that Itanium/IA64 has no maintainer, is no longer supported in
>> QEMU (for boot testing under emulation) and does not seem to have a user
>> base beyond a couple of machines used by distros to churn out packages,
>> let's mark it as dead. This shall mean that any treewide changes (such
>> as changes to the EFI subsystem, which I maintain) can be made even if
>> they might cause build or boot time regressions on IA64 machines. Also,
>> mark the port as scheduled for removal after the next LTS release.
>>
>
> Since this just came up, I very much prefer complete removal. I don't
> see the point of keeping dead code in the tree. That is still hidden
> maintenance effort.
>
> If this proliferates, we'll end up having to parse the MAINTAINERS file
> for code marked "Dead" to ensure that we don't accidentally send e-mails
> to the wrong people, or we risk getting complaints about sending reports
> for such code. That puts extra burden on maintainers of automated test
> beds, which I think is not really appropriate. If the code is dead,
> remove it, period.
>
> For my part, I'll drop my test bed support immediately after this patch
> made it in, following the guidance above.
I agree. While the idea of waiting for an LTS release makes sense
in general (and I did just that for the unused Arm board files), I
don't see how that would help with the timing here: The only remaining
distro with kernel updates is now Debian-ports, and the coming Bookwork
release will apparently use the 6.1-LTS kernel, but as I understand,
the mentioned (late-2023) LTS kernel will not be part either of the
following (mid-2025) Debian release or this one, so keeping it
for a year longer has all the extra cost without any real benefit.
Arnd
next prev parent reply other threads:[~2023-02-15 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 12:29 [RFC PATCH] MAINTAINERS: Mark Itanium/IA64 as 'dead' Ard Biesheuvel
2023-02-15 10:19 ` John Paul Adrian Glaubitz
2023-02-15 15:15 ` Guenter Roeck
2023-02-15 15:36 ` Arnd Bergmann [this message]
2023-02-15 15:40 ` Ard Biesheuvel
2023-02-15 17:08 ` Guenter Roeck
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=33201710-a18b-44a6-8e09-364f4a9ca5e5@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 read-only IMAP folder(s) and NNTP newsgroup(s).