From: Matthias Goergens <matthias.goergens@gmail.com>
To: "Tejun Heo" <tj@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Waiman Long" <longman@redhat.com>
Cc: Ridong Chen <ridong.chen@linux.dev>, cgroups@vger.kernel.org
Subject: [PATCH] MAINTAINERS: name the tj/cgroup for-next branch
Date: Thu, 24 Sep 2026 11:35:49 +0800 [thread overview]
Message-ID: <20260924033549.3625016-1-matthias.goergens@gmail.com> (raw)
The T: entries for CONTROL GROUP (CGROUP) and CONTROL GROUP - CPUSET
name tj/cgroup without a branch. The repository's HEAD (master,
11260c335ec6) is a commit from 2026-08-20 that mainline already
contains. linux-next pulls for-next from this repository (Next/Trees,
next-20260923), and on 2026-09-24 that branch carried work not yet in
mainline. Name the branch so the entries identify 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 at the wrong tree.
Signed-off-by: Matthias Goergens <matthias.goergens@gmail.com>
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index cc3cae2e378b..353e33d27e3e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -6647,7 +6647,7 @@ M: Johannes Weiner <hannes@cmpxchg.org>
M: Michal Koutný <mkoutny@suse.com>
L: cgroups@vger.kernel.org
S: Maintained
-T: git git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git
+T: git git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-next
F: Documentation/admin-guide/cgroup-v1/
F: Documentation/admin-guide/cgroup-v2.rst
F: include/linux/cgroup*
@@ -6674,7 +6674,7 @@ M: Waiman Long <longman@redhat.com>
R: Ridong Chen <ridong.chen@linux.dev>
L: cgroups@vger.kernel.org
S: Maintained
-T: git git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git
+T: git git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-next
F: Documentation/admin-guide/cgroup-v1/cpusets.rst
F: include/linux/cpuset.h
F: kernel/cgroup/cpuset-internal.h
base-commit: 40288c9206c17eb66a603262e06a58d300d0f279
--
2.55.0
reply other threads:[~2026-09-24 3:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260924033549.3625016-1-matthias.goergens@gmail.com \
--to=matthias.goergens@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=longman@redhat.com \
--cc=mkoutny@suse.com \
--cc=ridong.chen@linux.dev \
--cc=tj@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