Feedback-ID: i56a14606:Fastmail
User-Agent: Cyrus-JMAP/3.9.0-alpha0-156-g081acc5ed5-fm-20230206.001-g081acc5e
Mime-Version: 1.0
Message-Id: <33201710-a18b-44a6-8e09-364f4a9ca5e5@app.fastmail.com>
In-Reply-To: <20230215151547.GA3766362@roeck-us.net>
References: <20230128122904.1345120-1-ardb@kernel.org>
 <20230215151547.GA3766362@roeck-us.net>
Date:   Wed, 15 Feb 2023 16:36:23 +0100
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'
Content-Type: text/plain
Precedence: bulk

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