From: Maxime Ripard <mripard@kernel.org>
To: Simona Vetter <simona.vetter@ffwll.ch>,
David Airlie <airlied@gmail.com>,
Maarten Lankhorst <dev@lankhorst.se>,
Thomas Zimmermann <tzimmermann@suse.de>,
Maxime Ripard <mripard@kernel.org>
Cc: dri-devel@lists.freedesktop.org, Russell King <linux@armlinux.org.uk>
Subject: [PATCH 1/7] MAINTAINERS: Move armada DRM under drm-misc
Date: Thu, 5 Nov 2026 15:21:21 +0100 [thread overview]
Message-ID: <20261105142127.708219-1-mripard@kernel.org> (raw)
The armada DRM driver has its own tree entries in MAINTAINERS, pointing
to Russell King's drm-armada-devel and drm-armada-fixes branches.
However, the last pull request from that tree was sent in July 2019, and
more than 80 patches have been merged through drm-misc since then.
The driver is de facto maintained through drm-misc already.
Remove the dedicated tree entries and the drm-misc exclusion for
armada to reflect the actual maintenance path.
Signed-off-by: Maxime Ripard <mripard@kernel.org>
---
Cc: Russell King <linux@armlinux.org.uk>
---
MAINTAINERS | 3 ---
1 file changed, 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index c10342aa32f3..6856dd5a2b74 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8893,5 +8893,4 @@ F: include/linux/vga*
F: include/uapi/drm/
X: drivers/gpu/drm/amd/
-X: drivers/gpu/drm/armada/
X: drivers/gpu/drm/etnaviv/
X: drivers/gpu/drm/exynos/
@@ -16153,6 +16152,4 @@ MARVELL ARMADA DRM SUPPORT
M: Russell King <linux@armlinux.org.uk>
S: Maintained
-T: git git://git.armlinux.org.uk/~rmk/linux-arm.git drm-armada-devel
-T: git git://git.armlinux.org.uk/~rmk/linux-arm.git drm-armada-fixes
F: Documentation/devicetree/bindings/display/armada/
F: drivers/gpu/drm/armada/
--
2.55.0
next reply other threads:[~2026-11-05 14:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 14:21 Maxime Ripard [this message]
2026-11-05 14:21 ` [PATCH 2/7] MAINTAINERS: Move Keem Bay DRM under drm-misc Maxime Ripard
2026-11-05 14:54 ` Luca Ceresoli
2026-11-05 16:02 ` Thomas Zimmermann
2026-11-05 14:21 ` [PATCH 3/7] MAINTAINERS: Move Tegra " Maxime Ripard
2026-11-05 14:54 ` Luca Ceresoli
2026-11-05 16:03 ` Thomas Zimmermann
2026-11-05 14:21 ` [PATCH 4/7] MAINTAINERS: Remove Jonas Karlman from bridge reviewers Maxime Ripard
2026-11-05 15:13 ` Luca Ceresoli
2026-11-05 16:04 ` Thomas Zimmermann
2026-11-05 14:21 ` [PATCH 5/7] MAINTAINERS: Remove Andrzej Hajda from bridge maintainers Maxime Ripard
2026-11-05 15:13 ` Luca Ceresoli
2026-11-05 16:04 ` Thomas Zimmermann
2026-11-05 16:05 ` Thomas Zimmermann
2026-11-05 14:21 ` [PATCH 6/7] MAINTAINERS: Remove myself for VC4 DRM driver Maxime Ripard
2026-11-05 14:54 ` Luca Ceresoli
2026-11-05 16:06 ` Thomas Zimmermann
2026-11-05 16:19 ` Maíra Canal
2026-11-05 14:21 ` [PATCH 7/7] MAINTAINERS: Add Dmitry Baryshkov as bridge maintainer Maxime Ripard
2026-11-05 14:54 ` Luca Ceresoli
2026-11-05 16:07 ` Thomas Zimmermann
2026-11-05 14:54 ` [PATCH 1/7] MAINTAINERS: Move armada DRM under drm-misc Luca Ceresoli
2026-11-05 15:59 ` Thomas Zimmermann
2026-11-19 13:32 ` Maxime Ripard
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=20261105142127.708219-1-mripard@kernel.org \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=dev@lankhorst.se \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux@armlinux.org.uk \
--cc=simona.vetter@ffwll.ch \
--cc=tzimmermann@suse.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