From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, device@lanana.org, unicode@lanana.org,
"H . Peter Anvin" <hpa@zytor.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH 1/2] MAINTAINERS: remove historic section DEVICE NUMBER REGISTRY
Date: Tue, 7 Mar 2023 15:39:59 +0100 [thread overview]
Message-ID: <20230307144000.29539-2-lukas.bulwahn@gmail.com> (raw)
In-Reply-To: <20230307144000.29539-1-lukas.bulwahn@gmail.com>
As described in Documentation/admin-guide/devices.rst, the device number
registry (or linux device list) is at Documentation/admin-guide/devices.txt
and no longer maintained at lanana.org.
The devices.txt file is basically community-maintained, and there is no
other dedicated maintainer or contact for that file nowadays.
Remove the historic section DEVICE NUMBER REGISTRY in MAINTAINERS.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
Note: According to the get_maintainer script, Jonathan Corbet would be the
maintainer of those files, but probably everyone knows that the formal
role is really among various kernel developers, and not with Jon as
a benevolent dictator.
Jon, if that is fine for you, we just keep that with MAINTAINERS as-is.
Otherwise, I can send a specific change to exclude those two files,
Documentation/admin-guide/devices.{rst|txt} from the DOCUMENTATION
section in MAINTAINERS, but I do not see that critical, as only very little
changes happen to those files nowadays.
MAINTAINERS | 5 -----
1 file changed, 5 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 631fac6ab555..5d8f46f35aa4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5940,11 +5940,6 @@ F: drivers/devfreq/event/
F: include/dt-bindings/pmu/exynos_ppmu.h
F: include/linux/devfreq-event.h
-DEVICE NUMBER REGISTRY
-M: Torben Mathiasen <device@lanana.org>
-S: Maintained
-W: http://lanana.org/docs/device-list/index.html
-
DEVICE RESOURCE MANAGEMENT HELPERS
M: Hans de Goede <hdegoede@redhat.com>
R: Matti Vaittinen <mazziesaccount@gmail.com>
--
2.17.1
next prev parent reply other threads:[~2023-03-07 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 14:39 [PATCH 0/2] Updating information on lanana.org Lukas Bulwahn
2023-03-07 14:39 ` Lukas Bulwahn [this message]
2023-03-07 14:40 ` [PATCH 2/2] docs: admin: unicode: update information on state of lanana.org document Lukas Bulwahn
2023-03-14 18:30 ` [PATCH 0/2] Updating information on lanana.org Jonathan Corbet
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=20230307144000.29539-2-lukas.bulwahn@gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=corbet@lwn.net \
--cc=device@lanana.org \
--cc=hpa@zytor.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=unicode@lanana.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