From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Roberto Sassu <roberto.sassu@huawei.com>
Cc: zohar@linux.ibm.com, david.safford@ge.com, monty.wiseman@ge.com,
matthewgarrett@google.com, linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org, keyrings@vger.kernel.org,
linux-kernel@vger.kernel.org, silviu.vlasceanu@huawei.com
Subject: Re: [PATCH v10 0/6] tpm: retrieve digest size of unknown algorithms from TPM
Date: Wed, 6 Feb 2019 19:10:27 +0200 [thread overview]
Message-ID: <20190206171027.GA25668@linux.intel.com> (raw)
In-Reply-To: <3cd14c24-9de2-d347-b40c-22ca87d9df87@huawei.com>
On Wed, Feb 06, 2019 at 05:07:49PM +0100, Roberto Sassu wrote:
> Seems ok to me. I'll send patch 3/6 and 4/6.
Your series has been applied to master and next. Thank you.
/Jarkko
next prev parent reply other threads:[~2019-02-06 17:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 10:57 [PATCH v10 0/6] tpm: retrieve digest size of unknown algorithms from TPM Roberto Sassu
2019-02-06 10:57 ` [PATCH v10 1/6] tpm: dynamically allocate the allocated_banks array Roberto Sassu
2019-02-06 10:57 ` [PATCH v10 2/6] tpm: rename and export tpm2_digest and tpm2_algorithms Roberto Sassu
2019-02-06 10:57 ` [PATCH v10 3/6] tpm: retrieve digest size of unknown algorithms with PCR read Roberto Sassu
2019-02-06 10:57 ` [PATCH v10 4/6] tpm: move tpm_chip definition to include/linux/tpm.h Roberto Sassu
2019-02-06 10:57 ` [PATCH v10 5/6] KEYS: trusted: explicitly use tpm_chip structure from tpm_default_chip() Roberto Sassu
2019-02-06 10:57 ` [PATCH v10 6/6] tpm: pass an array of tpm_extend_digest structures to tpm_pcr_extend() Roberto Sassu
2019-02-06 12:57 ` [PATCH v10 0/6] tpm: retrieve digest size of unknown algorithms from TPM Jarkko Sakkinen
2019-02-06 13:07 ` Roberto Sassu
2019-02-06 13:54 ` Jarkko Sakkinen
2019-02-06 14:25 ` Roberto Sassu
2019-02-06 15:34 ` Jarkko Sakkinen
2019-02-06 16:07 ` Roberto Sassu
2019-02-06 17:10 ` Jarkko Sakkinen [this message]
2019-02-07 10:58 ` Roberto Sassu
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=20190206171027.GA25668@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=david.safford@ge.com \
--cc=keyrings@vger.kernel.org \
--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=roberto.sassu@huawei.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).