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

Hi Fan,

> 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.

Yes, nearly: since 28 September Sashiko skips such a HEAD and tries
linux-next first, then Linus' master.  linux-next is Linus' master plus
what is queued, so a patch based on master applies there unless it
conflicts with something queued, and then it falls back to master.
Either way it no longer reviews against a stale ipe master.  So please
drop this patch.

Thanks,
Matthias

      reply	other threads:[~2026-10-01 11:25 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
2026-10-01 11:25   ` Matthias Goergens [this message]

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=20261001112515.3822457-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