From: "Serge E. Hallyn" <serge@hallyn.com>
To: Paul Moore <paul@paul-moore.com>
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
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 16:52:51 -0500 [thread overview]
Message-ID: <20250310215251.GA196422@mail.hallyn.com> (raw)
In-Reply-To: <CAHC9VhTSdq=zrkmipZJjTMcudbyvHJeq+XR3Td7mr7cEn+GDEA@mail.gmail.com>
On Mon, Mar 10, 2025 at 05:36:54PM -0400, Paul Moore wrote:
> On Mon, Mar 10, 2025 at 5:32 PM Serge E. Hallyn <serge@hallyn.com> wrote:
> > On Mon, Mar 10, 2025 at 03:58:41PM -0400, Paul Moore wrote:
> > > 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!
> >
> > Oh, did I? I went back and forth, and actually *intended* M, but must
> > have left my git index out of sorts :) No problem - reviewer probably
> > makes more sense.
>
> The patch you posted to the mailing list had "R:" before your name :)
>
> I'm happy either way, if you would prefer a "M:" just let me know and
> I can update the commit.
R is fine - thanks.
prev parent reply other threads:[~2025-03-10 21:52 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
2025-03-10 21:32 ` Serge E. Hallyn
2025-03-10 21:36 ` Paul Moore
2025-03-10 21:52 ` 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=20250310215251.GA196422@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--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).