[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191101201957.GA8369@linux.intel.com>
Date: Fri, 1 Nov 2019 22:19:57 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Sumit Garg <sumit.garg@...aro.org>
Cc: Jens Wiklander <jens.wiklander@...aro.org>, dhowells@...hat.com,
Jonathan Corbet <corbet@....net>, jejb@...ux.ibm.com,
Mimi Zohar <zohar@...ux.ibm.com>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Casey Schaufler <casey@...aufler-ca.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Daniel Thompson <daniel.thompson@...aro.org>,
Stuart Yoder <stuart.yoder@....com>,
Janne Karhunen <janne.karhunen@...il.com>,
"open list:ASYMMETRIC KEYS" <keyrings@...r.kernel.org>,
linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org,
Linux Doc Mailing List <linux-doc@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
"tee-dev @ lists . linaro . org" <tee-dev@...ts.linaro.org>
Subject: Re: [Patch v3 6/7] doc: keys: Document usage of TEE based Trusted
Keys
On Fri, Nov 01, 2019 at 03:04:18PM +0530, Sumit Garg wrote:
> Isn't this statement contradicting with your earlier statement
> regarding the right order would be to complete TEE patches review
> first and then come up with documentation here [2]?
>
> [1] https://lore.kernel.org/linux-integrity/1568025601.4614.253.camel@linux.ibm.com/
> [2] https://lore.kernel.org/linux-integrity/20190909163643.qxmzpcggi567hmhv@linux.intel.com/
With the intersecting issues, namely key generation and conflicting
keyctl parameters, that was not a well considered statement.
/Jarkko
Powered by blists - more mailing lists