Linux Security Modules development
 help / color / mirror / Atom feed
From: Fan Wu <wufan@kernel.org>
To: Matthias Goergens <matthias.goergens@gmail.com>
Cc: linux-security-module@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: name the wufan/ipe next branch
Date: Mon, 28 Sep 2026 08:57:53 -0700	[thread overview]
Message-ID: <9699317a-df42-4ae0-986c-5602e66ae773@kernel.org> (raw)
In-Reply-To: <20260926055223.3678216-1-matthias.goergens@gmail.com>


On 9/25/2026 10:52 PM, Matthias Goergens wrote:
> 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

Hi Matthias,

From the related discussion, this looks intended to stop Sashiko from
picking a stale tree as its baseline.

For IPE, I only update next when there are patches queued, so it can
remain unchanged for several releases. Contributors should normally
base their work on Linus' master rather than next. Naming next here
could therefore lead to the same stale-baseline problem.

I also looked at your Sashiko PR. When the default HEAD is a strict
ancestor of Linus' master, would Sashiko use Linus' master instead?
If so, that's the behavior we want for IPE, and there would be no
need to add next here.

Fan

  reply	other threads:[~2026-09-28 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-26  5:52 [PATCH] MAINTAINERS: name the wufan/ipe next branch Matthias Goergens
2026-09-28 15:57 ` Fan Wu [this message]
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=9699317a-df42-4ae0-986c-5602e66ae773@kernel.org \
    --to=wufan@kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=matthias.goergens@gmail.com \
    /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