From: Roberto Sassu <roberto.sassu@huawei.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: <zohar@linux.ibm.com>, <david.safford@ge.com>,
<monty.wiseman@ge.com>, <linux-integrity@vger.kernel.org>,
<linux-security-module@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <silviu.vlasceanu@huawei.com>,
"Matthew Garrett" <matthewgarrett@google.com>
Subject: Re: [PATCH v7 5/5] tpm: pass an array of tpm_extend_digest structures to tpm_pcr_extend()
Date: Mon, 21 Jan 2019 14:50:49 +0100 [thread overview]
Message-ID: <e97d1377-b8d8-6ecb-4c7f-1b08235c6864@huawei.com> (raw)
In-Reply-To: <20190121123739.GD9423@linux.intel.com>
On 1/21/2019 1:37 PM, Jarkko Sakkinen wrote:
> 3. The would be nothing wrong exposing struct tpm_chip in
> include/linux/tpm.h. I would be totally fine with that.
Should I do it in a separate patch (before 5/5)?
Is it fine to call tpm_default_chip() only in pcrlock() for trusted
keys?
Thanks
Roberto
> /Jarkko
>
--
HUAWEI TECHNOLOGIES Duesseldorf GmbH, HRB 56063
Managing Director: Bo PENG, Jian LI, Yanli SHI
next prev parent reply other threads:[~2019-01-21 14:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 10:29 [PATCH v7 0/5] tpm: retrieve digest size of unknown algorithms from TPM Roberto Sassu
2018-12-13 10:29 ` [PATCH v7 1/5] tpm: dynamically allocate the allocated_banks array Roberto Sassu
2018-12-20 14:55 ` Jarkko Sakkinen
2018-12-21 9:40 ` Roberto Sassu
2018-12-22 0:03 ` Jarkko Sakkinen
2019-01-07 10:06 ` Roberto Sassu
2019-01-10 17:38 ` Jarkko Sakkinen
2019-01-11 7:53 ` Roberto Sassu
2019-01-11 16:35 ` Jarkko Sakkinen
2018-12-13 10:29 ` [PATCH v7 2/5] tpm: add _head suffix to tcg_efi_specid_event and tcg_pcr_event2 Roberto Sassu
2018-12-13 10:29 ` [PATCH v7 3/5] tpm: rename and export tpm2_digest and tpm2_algorithms Roberto Sassu
2018-12-13 10:29 ` [PATCH v7 4/5] tpm: retrieve digest size of unknown algorithms with PCR read Roberto Sassu
2018-12-13 10:29 ` [PATCH v7 5/5] tpm: pass an array of tpm_extend_digest structures to tpm_pcr_extend() Roberto Sassu
2018-12-20 15:21 ` Jarkko Sakkinen
2019-01-17 7:59 ` Roberto Sassu
2019-01-18 15:12 ` Jarkko Sakkinen
2019-01-21 8:11 ` Roberto Sassu
2019-01-21 12:30 ` Jarkko Sakkinen
2019-01-21 9:58 ` Roberto Sassu
2019-01-21 12:37 ` Jarkko Sakkinen
2019-01-21 13:50 ` Roberto Sassu [this message]
2019-01-22 16:55 ` Jarkko Sakkinen
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=e97d1377-b8d8-6ecb-4c7f-1b08235c6864@huawei.com \
--to=roberto.sassu@huawei.com \
--cc=david.safford@ge.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=matthewgarrett@google.com \
--cc=monty.wiseman@ge.com \
--cc=silviu.vlasceanu@huawei.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 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).