From: Matthias Goergens <matthias.goergens@gmail.com>
To: dlemoal@kernel.org, cassel@kernel.org
Cc: linux-ide@vger.kernel.org
Subject: [PATCH v2] MAINTAINERS: name the libata/linux for-next branch
Date: Fri, 25 Sep 2026 13:23:29 +0800 [thread overview]
Message-ID: <20260925052329.2683619-1-matthias.goergens@gmail.com> (raw)
In-Reply-To: <arTuIxpEsaYIQXU4@ryzen>
The T: entry for LIBATA SUBSYSTEM (Serial and Parallel ATA drivers)
names libata/linux without a branch. The repository's HEAD pointer
points to branch master, which has no active development. Active
development is on the for-next branch. Name the branch so the entry
identifies where development happens.
Documentation/process/submitting-patches.rst sends contributors to the
T: entry to find the tree to prepare patches against, so a branch-less
entry whose HEAD is already in mainline points them to the wrong branch.
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
Signed-off-by: Matthias Goergens <matthias.goergens@gmail.com>
---
Changes in v2:
- Reworded the commit message as Niklas Cassel suggested: no dates or
commit hashes, and "wrong branch" rather than "wrong tree".
- Kept Damien's Reviewed-by, as the diff is unchanged.
v1: https://lore.kernel.org/all/20260924033545.3624716-1-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..c9565f2c7644 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -14905,7 +14905,7 @@ M: Damien Le Moal <dlemoal@kernel.org>
M: Niklas Cassel <cassel@kernel.org>
L: linux-ide@vger.kernel.org
S: Maintained
-T: git git://git.kernel.org/pub/scm/linux/kernel/git/libata/linux.git
+T: git git://git.kernel.org/pub/scm/linux/kernel/git/libata/linux.git for-next
F: Documentation/ABI/testing/sysfs-ata
F: Documentation/devicetree/bindings/ata/
F: drivers/ata/
base-commit: 62f4c998b297cf233997a2b4cd6fc2d2df0319c9
--
2.55.0
next prev parent reply other threads:[~2026-09-25 5:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 3:35 [PATCH] MAINTAINERS: name the libata/linux for-next branch Matthias Goergens
2026-09-24 3:52 ` Damien Le Moal
2026-09-24 9:32 ` Niklas Cassel
2026-09-24 10:18 ` Matthias Goergens
2026-09-24 13:33 ` Niklas Cassel
2026-09-25 5:23 ` Matthias Goergens [this message]
2026-09-25 9:18 ` [PATCH v2] " Niklas Cassel
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=20260925052329.2683619-1-matthias.goergens@gmail.com \
--to=matthias.goergens@gmail.com \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@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