From: Petr Vorel <pvorel@suse.cz>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add missing "security/integrity" directory
Date: Wed, 19 Jan 2022 08:35:37 +0100 [thread overview]
Message-ID: <Yee/SaBeQMQBuIge@pevik> (raw)
In-Reply-To: <20220117230229.16475-1-zohar@linux.ibm.com>
Hi Mimi,
LGTM.
Reviewed-by: Petr Vorel <pvorel@suse.cz>
Few comments below.
> Update the IMA and EVM records to include the "security/integrity"
> directory.
> Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
> ---
> MAINTAINERS | 2 ++
> 1 file changed, 2 insertions(+)
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 5250298d2817..a9973d0991e3 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7181,6 +7181,7 @@ M: Mimi Zohar <zohar@linux.ibm.com>
> L: linux-integrity@vger.kernel.org
> S: Supported
Aren't you a maintainer? How about
S: Maintained
> F: security/integrity/evm/
> +F: security/integrity
I'd add trailing slash (i.e. security/integrity/)
How about adding git tree to EVM?
> EXTENSIBLE FIRMWARE INTERFACE (EFI)
> M: Ard Biesheuvel <ardb@kernel.org>
> @@ -9419,6 +9420,7 @@ L: linux-integrity@vger.kernel.org
> S: Supported
and here
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git
> F: security/integrity/ima/
> +F: security/integrity
and here
> INTEL 810/815 FRAMEBUFFER DRIVER
> M: Antonino Daplas <adaplas@gmail.com>
Kind regards,
Petr
prev parent reply other threads:[~2022-01-19 7:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 23:02 [PATCH] MAINTAINERS: add missing "security/integrity" directory Mimi Zohar
2022-01-19 7:35 ` Petr Vorel [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=Yee/SaBeQMQBuIge@pevik \
--to=pvorel@suse.cz \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=zohar@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.