From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Serge Semin <Sergey.Semin@baikalelectronics.ru>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH] MAINTAINERS: add section MIPS BAIKAL-T1 SOC DRIVERS
Date: Wed, 22 Nov 2023 06:41:42 +0100 [thread overview]
Message-ID: <20231122054142.31322-1-lukas.bulwahn@gmail.com> (raw)
In recent years, a number of drivers for the MIPS Baikal-T1 SoC have been
added to the kernel tree, but there is no dedicated MAINTAINERS section for
this SoC.
As all of the code has been contributed by Serge Semin, let us assume he is
still the active maintainer for this code rather than marking it orphan.
Add a new section MIPS BAIKAL-T1 SOC DRIVERS in MAINTAINERS.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
MAINTAINERS | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 9613c9c3cc97..820f1ab1ee80 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14474,6 +14474,19 @@ F: arch/mips/
F: drivers/platform/mips/
F: include/dt-bindings/mips/
+MIPS BAIKAL-T1 SOC DRIVERS
+M: Serge Semin <Sergey.Semin@baikalelectronics.ru>
+S: Maintained
+F: Documentation/hwmon/bt1-pvt.rst
+F: drivers/ata/ahci_dwc.c
+F: drivers/bus/bt1-*.c
+F: drivers/clk/baikal-t1/
+F: drivers/hwmon/bt1-pvt.[ch]
+F: drivers/memory/bt1-l2-ctl.c
+F: drivers/mtd/maps/physmap-bt1-rom.[ch]
+F: drivers/pci/controller/dwc/pcie-bt1.c
+F: drivers/spi/spi-dw-bt1.c
+
MIPS BOSTON DEVELOPMENT BOARD
M: Paul Burton <paulburton@kernel.org>
L: linux-mips@vger.kernel.org
--
2.17.1
next reply other threads:[~2023-11-22 5:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 5:41 Lukas Bulwahn [this message]
2023-11-22 13:32 ` Serge Semin
2023-11-22 13:49 ` Lukas Bulwahn
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=20231122054142.31322-1-lukas.bulwahn@gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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
all inboxes | Powered by JetHome®