linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: sergeh@kernel.org, linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add Serge Hallyn as maintainer for creds
Date: Mon, 10 Mar 2025 15:58:41 -0400	[thread overview]
Message-ID: <f44bad6065bbf45c02dc7caf90ed0e7e@paul-moore.com> (raw)
In-Reply-To: <Z82Sug-XLC1r5wKE@lei>

On Mar  9, 2025 sergeh@kernel.org wrote:
> 
> Also add the documentation file as suggested by Günther Noack.
> 
> Signed-off-by: Serge Hallyn <sergeh@kernel.org>
> ---
>  MAINTAINERS | 2 ++
>  1 file changed, 2 insertions(+)

I adjusted the subject line to reflect that you chose the reviewer role,
but otherwise this looks good, merged into lsm/dev.  Thanks!

> diff --git a/MAINTAINERS b/MAINTAINERS
> index 68e4656c15ea..54b47bfc4abd 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -6141,11 +6141,13 @@ F:	drivers/hid/hid-creative-sb0540.c
>  
>  CREDENTIALS
>  M:	Paul Moore <paul@paul-moore.com>
> +R:	Serge Hallyn <sergeh@kernel.org>
>  L:	linux-security-module@vger.kernel.org
>  S:	Supported
>  T:	git https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/lsm.git
>  F:	include/linux/cred.h
>  F:	kernel/cred.c
> +F:	Documentation/security/credentials.rst
>  
>  INTEL CRPS COMMON REDUNDANT PSU DRIVER
>  M:	Ninad Palsule <ninad@linux.ibm.com>
> -- 
> 2.34.1

--
paul-moore.com

  reply	other threads:[~2025-03-10 19:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-09 13:08 [PATCH] MAINTAINERS: add Serge Hallyn as maintainer for creds sergeh
2025-03-10 19:58 ` Paul Moore [this message]
2025-03-10 21:32   ` Serge E. Hallyn
2025-03-10 21:36     ` Paul Moore
2025-03-10 21:52       ` 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=f44bad6065bbf45c02dc7caf90ed0e7e@paul-moore.com \
    --to=paul@paul-moore.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@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).