From: Matthias Goergens <matthias.goergens@gmail.com>
To: Helge Deller <deller@gmx.de>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: [PATCH] MAINTAINERS: name the deller/linux-fbdev for-next branch
Date: Sun, 27 Sep 2026 13:12:56 +0800 [thread overview]
Message-ID: <20260927051256.2752154-1-matthias.goergens@gmail.com> (raw)
The T: entry for FRAMEBUFFER LAYER names deller/linux-fbdev without a
branch. The repository's HEAD points to branch master, which mainline
already contains. linux-next merges the for-next branch of this
repository (Next/Trees). Name that branch in the entry.
Signed-off-by: Matthias Goergens <matthias.goergens@gmail.com>
---
This is part of a cleanup of all T: entries whose repository HEAD is
not where development happens: one patch per repository, sent in small
batches. The plan is at [1], and why it goes out in batches at [2].
[1] https://lore.kernel.org/all/20260924033200.3615554-1-matthias.goergens@gmail.com/
[2] https://lore.kernel.org/all/20260924101844.2403008-1-matthias.goergens@gmail.com/
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 140eafcbbd78..b275a2254738 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10339,7 +10339,7 @@ L: linux-fbdev@vger.kernel.org
L: dri-devel@lists.freedesktop.org
S: Maintained
Q: http://patchwork.kernel.org/project/linux-fbdev/list/
-T: git git://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git
+T: git git://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git for-next
F: Documentation/fb/
F: drivers/video/
F: include/linux/fb.h
base-commit: 62f4c998b297cf233997a2b4cd6fc2d2df0319c9
--
2.55.0
next reply other threads:[~2026-09-27 5:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 5:12 Matthias Goergens [this message]
2026-09-27 13:38 ` [PATCH] MAINTAINERS: name the deller/linux-fbdev for-next branch Helge Deller
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=20260927051256.2752154-1-matthias.goergens@gmail.com \
--to=matthias.goergens@gmail.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.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