From: Jarkko Sakkinen <jarkko.sakkinen@linux•intel.com>
To: Sumit Garg <sumit.garg@linaro•org>
Cc: linux-security-module@vger•kernel.org,
daniel.thompson@linaro•org, op-tee@lists•trustedfirmware.org,
corbet@lwn•net, jejb@linux•ibm.com, janne.karhunen@gmail•com,
linux-doc@vger•kernel.org, jmorris@namei•org,
zohar@linux•ibm.com, linux-kernel@vger•kernel.org,
dhowells@redhat•com, lhinds@redhat•com, keyrings@vger•kernel.org,
Markus.Wamser@mixed-mode•de, casey@schaufler-ca•com,
linux-integrity@vger•kernel.org, jens.wiklander@linaro•org,
linux-arm-kernel@lists•infradead.org, serge@hallyn•com
Subject: Re: [PATCH v7 4/4] MAINTAINERS: Add entry for TEE based Trusted Keys
Date: Tue, 13 Oct 2020 05:21:57 +0300 [thread overview]
Message-ID: <20201013022157.GA47751@linux.intel.com> (raw)
In-Reply-To: <1602065268-26017-5-git-send-email-sumit.garg@linaro.org>
On Wed, Oct 07, 2020 at 03:37:48PM +0530, Sumit Garg wrote:
> Add MAINTAINERS entry for TEE based Trusted Keys framework.
>
> Signed-off-by: Sumit Garg <sumit.garg@linaro•org>
> Acked-by: Jarkko Sakkinen <jarkko.sakkinen@linux•intel.com>
> ---
> MAINTAINERS | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 48aff80..eb3d889 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -9663,6 +9663,14 @@ F: include/keys/trusted-type.h
> F: include/keys/trusted_tpm.h
> F: security/keys/trusted-keys/
>
> +KEYS-TRUSTED-TEE
> +M: Sumit Garg <sumit.garg@linaro•org>
> +L: linux-integrity@vger•kernel.org
> +L: keyrings@vger•kernel.org
> +S: Supported
> +F: include/keys/trusted_tee.h
> +F: security/keys/trusted-keys/trusted_tee.c
> +
> KEYS/KEYRINGS
> M: David Howells <dhowells@redhat•com>
> M: Jarkko Sakkinen <jarkko.sakkinen@linux•intel.com>
> --
> 2.7.4
I'm sorry but I think I have changed my mind on this. This has been
spinning for a while and sometimes conclusions change over the time.
I don't think that we really need a separate subsystem tag. I'd be for a
new M-entry or R-entry to the existing subsystem tag. It's essential to
have ack from someone with ARM and TEE knowledge but this way too heavy
for the purpose.
I also see it the most manageable if the trusted keys PR's come from a
single source.
/Jarkko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-10-13 2:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 10:07 [PATCH v7 0/4] Introduce TEE based Trusted Keys support Sumit Garg
2020-10-07 10:07 ` [PATCH v7 1/4] KEYS: trusted: Add generic trusted keys framework Sumit Garg
2020-10-13 1:43 ` Jarkko Sakkinen
2020-10-13 10:53 ` Sumit Garg
2020-10-13 11:59 ` Jarkko Sakkinen
2020-10-14 5:04 ` Sumit Garg
2020-10-21 3:21 ` Mimi Zohar
2020-10-21 5:46 ` Sumit Garg
2020-10-21 12:25 ` Mimi Zohar
2020-10-22 11:40 ` Sumit Garg
2020-10-07 10:07 ` [PATCH v7 2/4] KEYS: trusted: Introduce TEE based Trusted Keys Sumit Garg
2020-10-13 1:52 ` Jarkko Sakkinen
2020-10-13 11:01 ` Sumit Garg
2020-10-07 10:07 ` [PATCH v7 3/4] doc: trusted-encrypted: updates with TEE as a new trust source Sumit Garg
2020-10-07 10:07 ` [PATCH v7 4/4] MAINTAINERS: Add entry for TEE based Trusted Keys Sumit Garg
2020-10-13 2:21 ` Jarkko Sakkinen [this message]
2020-10-13 11:28 ` Sumit Garg
2020-10-13 13:40 ` Jarkko Sakkinen
2020-10-14 5:06 ` Sumit Garg
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=20201013022157.GA47751@linux.intel.com \
--to=jarkko.sakkinen@linux$(echo .)intel.com \
--cc=Markus.Wamser@mixed-mode$(echo .)de \
--cc=casey@schaufler-ca$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=daniel.thompson@linaro$(echo .)org \
--cc=dhowells@redhat$(echo .)com \
--cc=janne.karhunen@gmail$(echo .)com \
--cc=jejb@linux$(echo .)ibm.com \
--cc=jens.wiklander@linaro$(echo .)org \
--cc=jmorris@namei$(echo .)org \
--cc=keyrings@vger$(echo .)kernel.org \
--cc=lhinds@redhat$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-integrity@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-security-module@vger$(echo .)kernel.org \
--cc=op-tee@lists$(echo .)trustedfirmware.org \
--cc=serge@hallyn$(echo .)com \
--cc=sumit.garg@linaro$(echo .)org \
--cc=zohar@linux$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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