All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Ard Biesheuvel <ardb@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: [RFC PATCH] MAINTAINERS: Mark Itanium/IA64 as 'dead'
Date: Sat, 28 Jan 2023 13:29:04 +0100	[thread overview]
Message-ID: <20230128122904.1345120-1-ardb@kernel.org> (raw)

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.

Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Jessica Clarke <jrtc27@jrtc27.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Marc Zyngier <maz@kernel.org>
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-ia64@vger.kernel.org
Link: https://lore.kernel.org/all/CAMj1kXEqbMEcrKYzz2-huLPMnotPoxFY8adyH=Xb4Ex8o98x-w@mail.gmail.com/
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
---
 MAINTAINERS | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 5b74014994f5c1cc..5481967c2112e8ce 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -94,6 +94,14 @@ Descriptions of section entries and preferred order
 	   Obsolete:	Old code. Something tagged obsolete generally means
 			it has been replaced by a better system and you
 			should be using that.
+	   Dead:	Code has no maintainer and no significant user base,
+			and is scheduled for removal. Developers are free to
+			ignore it when it comes to testing bug fixes or other
+			code changes, and automated build test systems must not
+			report any detected issues, except possibly to mailing
+			lists or other recipients that have opted in
+			specifically to receiving reports about the state of
+			this code.
 	W: *Web-page* with status/info
 	Q: *Patchwork* web based patch tracking system site
 	B: URI for where to file *bugs*. A web-page with detailed bug
@@ -9833,7 +9841,7 @@ F:	include/linux/i3c/
 
 IA64 (Itanium) PLATFORM
 L:	linux-ia64@vger.kernel.org
-S:	Orphan
+S:	Dead # to be removed after the 2023 LTS release
 F:	Documentation/ia64/
 F:	arch/ia64/
 
-- 
2.39.0


WARNING: multiple messages have this Message-ID (diff)
From: Ard Biesheuvel <ardb@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Ard Biesheuvel <ardb@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: [RFC PATCH] MAINTAINERS: Mark Itanium/IA64 as 'dead'
Date: Sat, 28 Jan 2023 12:29:04 +0000	[thread overview]
Message-ID: <20230128122904.1345120-1-ardb@kernel.org> (raw)

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.

Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Jessica Clarke <jrtc27@jrtc27.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Marc Zyngier <maz@kernel.org>
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-ia64@vger.kernel.org
Link: https://lore.kernel.org/all/CAMj1kXEqbMEcrKYzz2-huLPMnotPoxFY8adyH=Xb4Ex8o98x-w@mail.gmail.com/
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
---
 MAINTAINERS | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 5b74014994f5c1cc..5481967c2112e8ce 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -94,6 +94,14 @@ Descriptions of section entries and preferred order
 	   Obsolete:	Old code. Something tagged obsolete generally means
 			it has been replaced by a better system and you
 			should be using that.
+	   Dead:	Code has no maintainer and no significant user base,
+			and is scheduled for removal. Developers are free to
+			ignore it when it comes to testing bug fixes or other
+			code changes, and automated build test systems must not
+			report any detected issues, except possibly to mailing
+			lists or other recipients that have opted in
+			specifically to receiving reports about the state of
+			this code.
 	W: *Web-page* with status/info
 	Q: *Patchwork* web based patch tracking system site
 	B: URI for where to file *bugs*. A web-page with detailed bug
@@ -9833,7 +9841,7 @@ F:	include/linux/i3c/
 
 IA64 (Itanium) PLATFORM
 L:	linux-ia64@vger.kernel.org
-S:	Orphan
+S:	Dead # to be removed after the 2023 LTS release
 F:	Documentation/ia64/
 F:	arch/ia64/
 
-- 
2.39.0

             reply	other threads:[~2023-01-28 12:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28 12:29 Ard Biesheuvel [this message]
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 10:19   ` John Paul Adrian Glaubitz
2023-02-15 15:15 ` Guenter Roeck
2023-02-15 15:15   ` Guenter Roeck
2023-02-15 15:36   ` Arnd Bergmann
2023-02-15 15:36     ` Arnd Bergmann
2023-02-15 15:40   ` Ard Biesheuvel
2023-02-15 15:40     ` Ard Biesheuvel
2023-02-15 17:08     ` Guenter Roeck
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=20230128122904.1345120-1-ardb@kernel.org \
    --to=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: 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.