From: Paul Moore <paul@paul-moore.com>
To: Anna Schumaker <anna@kernel.org>
Cc: Chuck Lever <cel@kernel.org>,
Trond Myklebust <trondmy@kernel.org>,
Jeff Layton <jlayton@kernel.org>,
Stephen Smalley <stephen.smalley.work@gmail.com>,
Achilles Gaikwad <achillesgaikwad@gmail.com>,
Casey Schaufler <casey@schaufler-ca.com>,
Christian Brauner <brauner@kernel.org>,
linux-nfs@vger.kernel.org,
linux-security-module@vger.kernel.org, selinux@vger.kernel.org
Subject: Re: [PATCH v2] security,fs,nfs,net: update security_inode_listsecurity() interface
Date: Fri, 31 Jul 2026 16:24:06 -0400 [thread overview]
Message-ID: <CAHC9VhQh5D_Py4c0JCzRWrcHbE5QSnencD7-mzzaZNyZGGE_NA@mail.gmail.com> (raw)
In-Reply-To: <33ba1c27-27cf-4b83-9c69-1ec40023a5d2@app.fastmail.com>
On Fri, Jul 31, 2026 at 1:28 PM Anna Schumaker <anna@kernel.org> wrote:
>
> Looks like I did have it in a branch with other commits for testing, but I
> never pushed it out. I've moved it over to my public linux-next and will
> pass it along to Linus in the next few days.
Perfect, thanks Anna!
--
paul-moore.com
prev parent reply other threads:[~2026-07-31 20:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 19:50 [PATCH v2] security,fs,nfs,net: update security_inode_listsecurity() interface Stephen Smalley
2025-04-29 7:46 ` Christian Brauner
2025-04-29 12:25 ` Stephen Smalley
2025-04-29 23:34 ` Paul Moore
2025-05-20 21:31 ` Paul Moore
2025-05-21 0:22 ` Casey Schaufler
2025-05-27 21:03 ` Anna Schumaker
2025-06-19 21:18 ` Paul Moore
2025-07-24 2:09 ` Paul Moore
2025-12-03 15:35 ` Stephen Smalley
2025-12-03 15:55 ` Paul Moore
2025-12-03 18:08 ` Stephen Smalley
2025-12-03 20:01 ` Stephen Smalley
2025-06-05 18:09 ` Stephen Smalley
2025-06-05 18:24 ` Paul Moore
2025-05-21 0:31 ` Kuniyuki Iwashima
2025-06-19 21:04 ` Paul Moore
2025-06-06 13:39 ` Konstantin Andreev
2025-06-06 14:28 ` Stephen Smalley
2025-06-06 15:24 ` Konstantin Andreev
2026-04-28 19:21 ` [PATCH ported/repost " Paul Moore
2026-04-28 19:26 ` Paul Moore
2026-05-01 16:00 ` Paul Moore
2026-07-25 20:14 ` [PATCH " Chuck Lever
2026-07-26 15:03 ` Paul Moore
2026-07-26 18:31 ` Paul Moore
2026-07-31 16:09 ` Paul Moore
2026-07-31 17:07 ` Chuck Lever
2026-07-31 17:28 ` Anna Schumaker
2026-07-31 20:24 ` Paul Moore [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=CAHC9VhQh5D_Py4c0JCzRWrcHbE5QSnencD7-mzzaZNyZGGE_NA@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=achillesgaikwad@gmail.com \
--cc=anna@kernel.org \
--cc=brauner@kernel.org \
--cc=casey@schaufler-ca.com \
--cc=cel@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=trondmy@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