From: Paul Moore <paul@paul-moore.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: joe@perches.com, linux-kernel@vger.kernel.org,
Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
selinux@vger.kernel.org, keescook@chromium.org
Subject: Re: [PATCH] Bad file pattern in 'SELINUX SECURITY MODULE'
Date: Fri, 29 Mar 2019 09:33:16 -0400 [thread overview]
Message-ID: <CAHC9VhReNxpWNg6WfCShRijO+AWC9TR8dzCP8COwz_Qe0xr4wA@mail.gmail.com> (raw)
In-Reply-To: <CAHC9VhRJUxnEyFvJQ3PR+aQTnGt=GZ+EZ-oBQihEE9WgQ9n5EA@mail.gmail.com>
On Mon, Mar 25, 2019 at 7:52 PM Paul Moore <paul@paul-moore.com> wrote:
> On Mon, Mar 25, 2019 at 7:21 PM Casey Schaufler <casey@schaufler-ca.com> wrote:
> > The include/linux/selinux.h file has been removed.
> > Remove the entry from the MAINTAINERS file.
> >
> > Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
> > ---
> > MAINTAINERS | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 3e5a5d263f29..1039c34dff3c 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -13947,7 +13947,6 @@ W: https://selinuxproject.org
> > W: https://github.com/SELinuxProject
> > T: git git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
> > S: Supported
> > -F: include/linux/selinux*
>
> This is fine with me, but if we're updating this file, we should
> probably add the following:
>
> F: include/uapi/linux/selinux_netlink.h
Are you going to update this Casey or should I?
> > F: security/selinux/
> > F: scripts/selinux/
> > F: Documentation/admin-guide/LSM/SELinux.rst
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2019-03-29 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 23:21 [PATCH] Bad file pattern in 'SELINUX SECURITY MODULE' Casey Schaufler
2019-03-25 23:52 ` Paul Moore
2019-03-29 13:33 ` Paul Moore [this message]
2019-03-29 15:22 ` Casey Schaufler
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=CAHC9VhReNxpWNg6WfCShRijO+AWC9TR8dzCP8COwz_Qe0xr4wA@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=casey@schaufler-ca.com \
--cc=eparis@parisplace.org \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@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).