MAINTAINERS: Mark Itanium/IA64 as 'dead'
RFC PATCH 1/1 MAINTAINERS: Mark Itanium/IA64 as 'dead'
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.
--- MAINTAINERS | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
MAINTAINERS +9 -1
@@ -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: [email protected] -S: Orphan +S: Dead # to be removed after the 2023 LTS release F: Documentation/ia64/ F: arch/ia64/
Signature · 1 line
2.39.0
Hello Ard!
Quoted 50 lines · Ard Biesheuvel
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 <[email protected]>Cc Arnd Bergmann <[email protected]>Cc Tony Luck <[email protected]>Cc Jessica Clarke <[email protected]>Cc John Paul Adrian Glaubitz <[email protected]>Cc Matthew Wilcox <[email protected]>Cc Marc Zyngier <[email protected]>Cc Guenter Roeck <[email protected]>Cc Linus Torvalds <[email protected]>Link https://lore.kernel.org/all/CAMj1kXEqbMEcrKYzz2-huLPMnotPoxFY8adyH=Xb4Ex8o98x-w@mail.gmail.com/ open hereSigned-off-by Ard Biesheuvel <[email protected]>--- MAINTAINERS | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)MAINTAINERS +8
-0@@ -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
MAINTAINERS F: include/linux/i3c/ · line 9846
Quoted 7 lines
MAINTAINERS +1
-1@@ -9833,7 +9841,7 @@ F: include/linux/i3c/ IA64 (Itanium) PLATFORM L: [email protected] -S: Orphan +S: Dead # to be removed after the 2023 LTS release F: Documentation/ia64/ F: arch/ia64/
Sounds reasonable to me.
Adrian
Signature · 4 lines
.''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Quoted 6 lines · Ard Biesheuvel
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.
Quoted 8 lines
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.
Guenter
Quoted 47 lines
Cc Jonathan Corbet <[email protected]>Cc Arnd Bergmann <[email protected]>Cc Tony Luck <[email protected]>Cc Jessica Clarke <[email protected]>Cc John Paul Adrian Glaubitz <[email protected]>Cc Matthew Wilcox <[email protected]>Cc Marc Zyngier <[email protected]>Cc Guenter Roeck <[email protected]>Cc Linus Torvalds <[email protected]>Link https://lore.kernel.org/all/CAMj1kXEqbMEcrKYzz2-huLPMnotPoxFY8adyH=Xb4Ex8o98x-w@mail.gmail.com/ open hereSigned-off-by Ard Biesheuvel <[email protected]>--- MAINTAINERS | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)MAINTAINERS +9
-1@@ -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: [email protected] -S: Orphan +S: Dead # to be removed after the 2023 LTS release F: Documentation/ia64/ F: arch/ia64/Signature · 1 line
2.39.0
Quoted 27 lines · Guenter Roeck
Quoted 6 lines · Ard Biesheuvel
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.
Quoted 8 lines
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
MAINTAINERSfile 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.
Quoted 2 lines
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
Quoted 17 lines · Guenter Roeck
Quoted 6 lines · Ard Biesheuvel
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.
Quoted 8 lines
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.
Quoted 4 lines
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.
Can I take this as an ack on
https://lore.kernel.org/linux-kernel/[email protected]/
?
Quoted 10 lines
If this proliferates, we'll end up having to parse the
MAINTAINERSfile 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.
Thanks for the insight. I think we should take the immediate removal route.
Quoted 18 lines · Ard Biesheuvel
Quoted 17 lines · Guenter Roeck
Quoted 14 lines · Ard Biesheuvel
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.
Quoted 9 lines
Quoted 4 lines
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.
Can I take this as an ack on
I would not have considered myself important enough to make such a call, but from a testbed maintainer's perspective it is an enthusiastic yes.
At the same time, again from a testbed maintainer's perspective, introducing a new "dead" state into the code base deserves a just as enthusiastic NACK.
Thanks,
Guenter
Quoted 14 lines
?
Quoted 10 lines
If this proliferates, we'll end up having to parse the
MAINTAINERSfile 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.
Thanks for the insight. I think we should take the immediate removal route.