From: sergeh@kernel.org
To: Paul Moore <paul@paul-moore.com>
Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [RFC PATCH] MAINTAINERS: add an explicit credentials entry
Date: Sat, 8 Mar 2025 02:47:08 +0000 [thread overview]
Message-ID: <Z8uvrJRfu4-0lk-I@lei> (raw)
In-Reply-To: <CAHC9VhRW4Be+uBbtgCRvSkUj1-CtYFZ9jbD9MZM70i7GhF624Q@mail.gmail.com>
On Fri, Mar 07, 2025 at 12:13:08PM -0500, Paul Moore wrote:
> On Tue, Mar 4, 2025 at 5:23 PM Paul Moore <paul@paul-moore.com> wrote:
> >
> > The lack of an explicit credential (kernel/cred.c) entry has caused
> > confusion in the past among new, and not-so-new developers, about where
> > to send credential patches for discussion and merging. Those patches
> > that are sent can often rot on the mailing lists for months as there
> > is no clear maintainer tasked with reviewing and merging patches.
> >
> > I'm volunteering for the cred maintainer role to try and reduce the
> > confusion and help cred patches find their way up to Linus' tree. As
> > there generally aren't a lot of cred patches I'll start with simply
> > folding them into the LSM tree, but if this changes I'll setup a
> > dedicated cred tree.
> >
> > Signed-off-by: Paul Moore <paul@paul-moore.com>
> > ---
> > MAINTAINERS | 8 ++++++++
> > 1 file changed, 8 insertions(+)
>
> I haven't seen any objections, or any other volunteers, so I'm going
> to go ahead and merge this to send up to Linus during the upcoming
> merge window.
Sorry, I managed to not take my personal laptop charger with me
on a trip this week, fell behind.
I'm very happy with you as the maintainer, but I do volunteer to
try and step in here, if that works.
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 896a307fa065..68e4656c15ea 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -6139,6 +6139,14 @@ L: linux-input@vger.kernel.org
> > S: Maintained
> > F: drivers/hid/hid-creative-sb0540.c
> >
> > +CREDENTIALS
> > +M: Paul Moore <paul@paul-moore.com>
> > +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
> > +
> > INTEL CRPS COMMON REDUNDANT PSU DRIVER
> > M: Ninad Palsule <ninad@linux.ibm.com>
> > L: linux-hwmon@vger.kernel.org
> > --
> > 2.48.1
>
> --
> paul-moore.com
next prev parent reply other threads:[~2025-03-08 2:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 22:23 [RFC PATCH] MAINTAINERS: add an explicit credentials entry Paul Moore
2025-03-07 17:13 ` Paul Moore
2025-03-08 2:47 ` sergeh [this message]
2025-03-08 17:01 ` Paul Moore
2025-03-09 11:12 ` Günther Noack
2025-03-10 20:29 ` Paul Moore
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=Z8uvrJRfu4-0lk-I@lei \
--to=sergeh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
/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).