From: "Serge E. Hallyn" <serge@hallyn.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Christian Göttsche" <cgzones@googlemail.com>,
"Serge Hallyn" <sergeh@kernel.org>,
"Christian Brauner" <brauner@kernel.org>,
"Paul Moore" <paul@paul-moore.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
selinux@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: Missing signoff in the capabilities-next tree
Date: Mon, 15 Sep 2025 12:10:42 -0500 [thread overview]
Message-ID: <aMhIkinrQtnFz1/c@mail.hallyn.com> (raw)
In-Reply-To: <bb5c5c5f-fa31-4339-aa53-d06596351f86@sirena.org.uk>
On Mon, Sep 15, 2025 at 05:04:40PM +0100, Mark Brown wrote:
> Commit
>
> d87d3c530e0ce ("pid: use ns_capable_noaudit() when determining net sysctl permissions")
>
> in the capabilites-next tree is missing a Signed-off-by from its
> committer.
Hm, I had expected b4 shazam to do that for me, but I see that
that requires -s.
In any case, I think I will be dropping it from this tree, and
Christian will take it through his.
thanks,
-serge
prev parent reply other threads:[~2025-09-15 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 16:04 Missing signoff in the capabilities-next tree Mark Brown
2025-09-15 17:10 ` Serge E. Hallyn [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=aMhIkinrQtnFz1/c@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=cgzones@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=sergeh@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).