linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: linux-security-module@vger.kernel.org, James Morris <jmorris@namei.org>
Subject: [PATCH] MAINTAINERS: update the LSM maintainer info
Date: Fri, 08 Jul 2022 16:34:46 -0400	[thread overview]
Message-ID: <165731248606.335227.15503387932450699761.stgit@olly> (raw)

After many years of shepherding the LSM layer, and Linux kernel
access control in general, James has decided to take a small step
away from his technical role and has asked me to assume the
day-to-day maintenance tasks for the LSM.  This patch makes the
necessary updates to the MAINTAINERS file.

Thanks for all you patience and stewardship over the years James,
I promise to do my best not to screw it all up :)

Cc: linux-security-module@vger.kernel.org
Signed-off-by: Paul Moore <paul@paul-moore.com>
---
 MAINTAINERS |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index a6d3bd9d2a8d..5c7c5d04b99d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -17909,12 +17909,13 @@ S:	Supported
 F:	Documentation/admin-guide/security-bugs.rst
 
 SECURITY SUBSYSTEM
+M:	Paul Moore <paul@paul-moore.com>
 M:	James Morris <jmorris@namei.org>
 M:	"Serge E. Hallyn" <serge@hallyn.com>
 L:	linux-security-module@vger.kernel.org (suggested Cc:)
 S:	Supported
 W:	http://kernsec.org/
-T:	git git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/lsm.git
 F:	security/
 X:	security/selinux/
 


             reply	other threads:[~2022-07-08 20:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 20:34 Paul Moore [this message]
2022-07-08 20:39 ` [PATCH] MAINTAINERS: update the LSM maintainer info Casey Schaufler
2022-07-08 21:00 ` James Morris
2022-07-10 14:06   ` Paul Moore
2022-07-11 16:16     ` James Morris
2022-07-11 17:49       ` Paul Moore
2022-07-10 14:15 ` Serge E. Hallyn

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=165731248606.335227.15503387932450699761.stgit@olly \
    --to=paul@paul-moore.com \
    --cc=jmorris@namei.org \
    --cc=linux-security-module@vger.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).