From: Matthias Goergens <matthias.goergens@gmail.com>
To: Fan Wu <wufan@kernel.org>
Cc: linux-security-module@vger.kernel.org
Subject: [PATCH] MAINTAINERS: name the wufan/ipe next branch
Date: Sat, 26 Sep 2026 13:52:23 +0800 [thread overview]
Message-ID: <20260926055223.3678216-1-matthias.goergens@gmail.com> (raw)
The T: entry for INTEGRITY POLICY ENFORCEMENT (IPE) names wufan/ipe
without a branch. The repository's HEAD points to branch master, which
mainline already contains. linux-next merges the 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..fc42b68e0718 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -12960,7 +12960,7 @@ INTEGRITY POLICY ENFORCEMENT (IPE)
M: Fan Wu <wufan@kernel.org>
L: linux-security-module@vger.kernel.org
S: Supported
-T: git git://git.kernel.org/pub/scm/linux/kernel/git/wufan/ipe.git
+T: git git://git.kernel.org/pub/scm/linux/kernel/git/wufan/ipe.git next
F: Documentation/admin-guide/LSM/ipe.rst
F: Documentation/security/ipe.rst
F: scripts/ipe/
base-commit: 62f4c998b297cf233997a2b4cd6fc2d2df0319c9
--
2.55.0
next reply other threads:[~2026-09-26 5:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 5:52 Matthias Goergens [this message]
2026-09-28 15:57 ` [PATCH] MAINTAINERS: name the wufan/ipe next branch Fan Wu
2026-10-01 11:25 ` Matthias Goergens
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=20260926055223.3678216-1-matthias.goergens@gmail.com \
--to=matthias.goergens@gmail.com \
--cc=linux-security-module@vger.kernel.org \
--cc=wufan@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;
as well as URLs for NNTP newsgroup(s).