diff for duplicates of <1591108981.4253.17.camel@linux.ibm.com> diff --git a/a/1.txt b/N1/1.txt index 25ebf99..8972b5b 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -12,9 +12,11 @@ TEE and TPM what should it do? Things like this: > @@ -25,6 +25,8 @@ > > #if defined(CONFIG_TRUSTED_TPM) -> static struct trusted_key_ops *trusted_key_ops > &tpm_trusted_key_ops; +> static struct trusted_key_ops *trusted_key_ops = +> &tpm_trusted_key_ops; > +#elif defined(CONFIG_TRUSTED_TEE) -> +static struct trusted_key_ops *trusted_key_ops > &tee_trusted_key_ops; +> +static struct trusted_key_ops *trusted_key_ops = +> &tee_trusted_key_ops; > #else Say it's either/or at a Kconfig level: so if you select both TEE and diff --git a/a/content_digest b/N1/content_digest index 0e4eb07..de7e12e 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,27 +1,27 @@ "ref\01591107505-6030-1-git-send-email-sumit.garg@linaro.org\0" "From\0James Bottomley <jejb@linux.ibm.com>\0" "Subject\0Re: [PATCH v5 0/4] Introduce TEE based Trusted Keys support\0" - "Date\0Tue, 02 Jun 2020 14:43:01 +0000\0" + "Date\0Tue, 02 Jun 2020 07:43:01 -0700\0" "To\0Sumit Garg <sumit.garg@linaro.org>" jarkko.sakkinen@linux.intel.com " zohar@linux.ibm.com\0" - "Cc\0tee-dev@lists.linaro.org" - daniel.thompson@linaro.org - op-tee@lists.trustedfirmware.org + "Cc\0dhowells@redhat.com" + jens.wiklander@linaro.org corbet@lwn.net - janne.karhunen@gmail.com - linux-doc@vger.kernel.org jmorris@namei.org - linux-kernel@vger.kernel.org - dhowells@redhat.com - linux-security-module@vger.kernel.org - keyrings@vger.kernel.org - Markus.Wamser@mixed-mode.de + serge@hallyn.com casey@schaufler-ca.com + janne.karhunen@gmail.com + daniel.thompson@linaro.org + Markus.Wamser@mixed-mode.de + keyrings@vger.kernel.org linux-integrity@vger.kernel.org - jens.wiklander@linaro.org + linux-security-module@vger.kernel.org + linux-doc@vger.kernel.org + linux-kernel@vger.kernel.org linux-arm-kernel@lists.infradead.org - " serge@hallyn.com\0" + op-tee@lists.trustedfirmware.org + " tee-dev@lists.linaro.org\0" "\00:1\0" "b\0" "On Tue, 2020-06-02 at 19:48 +0530, Sumit Garg wrote:\n" @@ -38,9 +38,11 @@ "> @@ -25,6 +25,8 @@\n" "> \n" "> #if defined(CONFIG_TRUSTED_TPM)\n" - "> static struct trusted_key_ops *trusted_key_ops > &tpm_trusted_key_ops;\n" + "> static struct trusted_key_ops *trusted_key_ops =\n" + "> &tpm_trusted_key_ops;\n" "> +#elif defined(CONFIG_TRUSTED_TEE)\n" - "> +static struct trusted_key_ops *trusted_key_ops > &tee_trusted_key_ops;\n" + "> +static struct trusted_key_ops *trusted_key_ops =\n" + "> &tee_trusted_key_ops;\n" "> #else\n" "\n" "Say it's either/or at a Kconfig level: so if you select both TEE and\n" @@ -60,4 +62,4 @@ "\n" James -57f71f27bf88c399e09aa80a96dc9efe777c3f7aef69bc000f231df48a0c76d0 +5f9672ce84ea1062056c49ea263d566d201de5f7a86c70a93ae26ea7d1aa3b83
diff --git a/a/1.txt b/N2/1.txt index 25ebf99..8972b5b 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -12,9 +12,11 @@ TEE and TPM what should it do? Things like this: > @@ -25,6 +25,8 @@ > > #if defined(CONFIG_TRUSTED_TPM) -> static struct trusted_key_ops *trusted_key_ops > &tpm_trusted_key_ops; +> static struct trusted_key_ops *trusted_key_ops = +> &tpm_trusted_key_ops; > +#elif defined(CONFIG_TRUSTED_TEE) -> +static struct trusted_key_ops *trusted_key_ops > &tee_trusted_key_ops; +> +static struct trusted_key_ops *trusted_key_ops = +> &tee_trusted_key_ops; > #else Say it's either/or at a Kconfig level: so if you select both TEE and diff --git a/a/content_digest b/N2/content_digest index 0e4eb07..229fe05 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,28 +1,9 @@ "ref\01591107505-6030-1-git-send-email-sumit.garg@linaro.org\0" "From\0James Bottomley <jejb@linux.ibm.com>\0" - "Subject\0Re: [PATCH v5 0/4] Introduce TEE based Trusted Keys support\0" - "Date\0Tue, 02 Jun 2020 14:43:01 +0000\0" - "To\0Sumit Garg <sumit.garg@linaro.org>" - jarkko.sakkinen@linux.intel.com - " zohar@linux.ibm.com\0" - "Cc\0tee-dev@lists.linaro.org" - daniel.thompson@linaro.org - op-tee@lists.trustedfirmware.org - corbet@lwn.net - janne.karhunen@gmail.com - linux-doc@vger.kernel.org - jmorris@namei.org - linux-kernel@vger.kernel.org - dhowells@redhat.com - linux-security-module@vger.kernel.org - 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\0" - "\00:1\0" + "Subject\0Re: [op-tee] [PATCH v5 0/4] Introduce TEE based Trusted Keys support\0" + "Date\0Tue, 02 Jun 2020 07:43:01 -0700\0" + "To\0op-tee@lists.trustedfirmware.org\0" + "\01:1\0" "b\0" "On Tue, 2020-06-02 at 19:48 +0530, Sumit Garg wrote:\n" "> Add support for TEE based trusted keys where TEE provides the\n" @@ -38,9 +19,11 @@ "> @@ -25,6 +25,8 @@\n" "> \n" "> #if defined(CONFIG_TRUSTED_TPM)\n" - "> static struct trusted_key_ops *trusted_key_ops > &tpm_trusted_key_ops;\n" + "> static struct trusted_key_ops *trusted_key_ops =\n" + "> &tpm_trusted_key_ops;\n" "> +#elif defined(CONFIG_TRUSTED_TEE)\n" - "> +static struct trusted_key_ops *trusted_key_ops > &tee_trusted_key_ops;\n" + "> +static struct trusted_key_ops *trusted_key_ops =\n" + "> &tee_trusted_key_ops;\n" "> #else\n" "\n" "Say it's either/or at a Kconfig level: so if you select both TEE and\n" @@ -60,4 +43,4 @@ "\n" James -57f71f27bf88c399e09aa80a96dc9efe777c3f7aef69bc000f231df48a0c76d0 +ab6a86ba28f452bd81325fdad60a650165393bb10714267912b01e16d26d188d
diff --git a/a/1.txt b/N3/1.txt index 25ebf99..432f9bc 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -12,9 +12,11 @@ TEE and TPM what should it do? Things like this: > @@ -25,6 +25,8 @@ > > #if defined(CONFIG_TRUSTED_TPM) -> static struct trusted_key_ops *trusted_key_ops > &tpm_trusted_key_ops; +> static struct trusted_key_ops *trusted_key_ops = +> &tpm_trusted_key_ops; > +#elif defined(CONFIG_TRUSTED_TEE) -> +static struct trusted_key_ops *trusted_key_ops > &tee_trusted_key_ops; +> +static struct trusted_key_ops *trusted_key_ops = +> &tee_trusted_key_ops; > #else Say it's either/or at a Kconfig level: so if you select both TEE and @@ -33,3 +35,9 @@ to upstream, at least for TPM keys, but do TEE keys have a recognized ASN.1 format? James + + +_______________________________________________ +linux-arm-kernel mailing list +linux-arm-kernel@lists.infradead.org +http://lists.infradead.org/mailman/listinfo/linux-arm-kernel diff --git a/a/content_digest b/N3/content_digest index 0e4eb07..26f194a 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -1,7 +1,7 @@ "ref\01591107505-6030-1-git-send-email-sumit.garg@linaro.org\0" "From\0James Bottomley <jejb@linux.ibm.com>\0" "Subject\0Re: [PATCH v5 0/4] Introduce TEE based Trusted Keys support\0" - "Date\0Tue, 02 Jun 2020 14:43:01 +0000\0" + "Date\0Tue, 02 Jun 2020 07:43:01 -0700\0" "To\0Sumit Garg <sumit.garg@linaro.org>" jarkko.sakkinen@linux.intel.com " zohar@linux.ibm.com\0" @@ -38,9 +38,11 @@ "> @@ -25,6 +25,8 @@\n" "> \n" "> #if defined(CONFIG_TRUSTED_TPM)\n" - "> static struct trusted_key_ops *trusted_key_ops > &tpm_trusted_key_ops;\n" + "> static struct trusted_key_ops *trusted_key_ops =\n" + "> &tpm_trusted_key_ops;\n" "> +#elif defined(CONFIG_TRUSTED_TEE)\n" - "> +static struct trusted_key_ops *trusted_key_ops > &tee_trusted_key_ops;\n" + "> +static struct trusted_key_ops *trusted_key_ops =\n" + "> &tee_trusted_key_ops;\n" "> #else\n" "\n" "Say it's either/or at a Kconfig level: so if you select both TEE and\n" @@ -58,6 +60,12 @@ "to upstream, at least for TPM keys, but do TEE keys have a recognized\n" "ASN.1 format?\n" "\n" - James + "James\n" + "\n" + "\n" + "_______________________________________________\n" + "linux-arm-kernel mailing list\n" + "linux-arm-kernel@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -57f71f27bf88c399e09aa80a96dc9efe777c3f7aef69bc000f231df48a0c76d0 +41e2e134ab5ab70f2c018fdb974c579b20192cfcd0f3c92097df7f6c4117f6f2
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.