From: Joe Perches <joe@perches.com>
To: Casey Schaufler <casey@schaufler-ca.com>, linux-kernel@vger.kernel.org
Cc: Paul Moore <paul@paul-moore.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
selinux@vger.kernel.org, Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] Bad file pattern in MAINTAINERS section 'SELINUX SECURITY MODULE'
Date: Mon, 25 Mar 2019 15:02:48 -0700 [thread overview]
Message-ID: <8a54298538371340d0a7fe762e742a88e12f43ba.camel@perches.com> (raw)
In-Reply-To: <a0847fd8-0b9b-69f5-e9b8-1e1cd3b5052d@schaufler-ca.com>
On Mon, 2019-03-25 at 14:58 -0700, Casey Schaufler wrote:
> The include/linux/selinux.h file has been removed.
> Remove the entry from the MAINTAINERS file.
This looks like it doesn't apply correctly as there
are one too many spaces before each context lines.
> 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*
> F: security/selinux/
> F: scripts/selinux/
> F: Documentation/admin-guide/LSM/SELinux.rst
>
next prev parent reply other threads:[~2019-03-25 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7cd8d12f59bcacd18a78f599b46dac555f7f16c0.camel@perches.com>
2019-03-25 21:27 ` Bad file pattern in MAINTAINERS section 'SELINUX SECURITY MODULE' Joe Perches
2019-03-25 21:58 ` [PATCH] " Casey Schaufler
2019-03-25 22:02 ` Joe Perches [this message]
2019-03-25 22: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=8a54298538371340d0a7fe762e742a88e12f43ba.camel@perches.com \
--to=joe@perches.com \
--cc=casey@schaufler-ca.com \
--cc=eparis@parisplace.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--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).