From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Alexander Steffen <Alexander.Steffen@infineon.com>
Cc: tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH RESEND v2 0/3] tpm2-cmd: Improve self test execution
Date: Sat, 2 Sep 2017 13:16:44 +0300 [thread overview]
Message-ID: <20170902101644.x254cv2jmlw3jruu@linux.intel.com> (raw)
In-Reply-To: <20170831171858.13252-1-Alexander.Steffen@infineon.com>
On Thu, Aug 31, 2017 at 07:18:55PM +0200, Alexander Steffen wrote:
> The self test logic for TPM 2.0 was probably based on the implementation
> for TPM 1.2, but did not correctly take into account some TPM 2.0 specifics.
> This patch series fixes those issues.
>
> v2:
> - Moved implementation description from comment to commit message.
>
> Alexander Steffen (3):
> tpm2-cmd: Trigger only missing self tests
> tpm2-cmd: Use dynamic delay to wait for self test result
> tpm2-cmd: React correctly to RC_TESTING from self tests
>
> drivers/char/tpm/tpm2-cmd.c | 69 +++++++++++++--------------------------------
> 1 file changed, 20 insertions(+), 49 deletions(-)
>
> --
> 2.7.4
>
Great, just have to test these.
/Jarkko
next prev parent reply other threads:[~2017-09-02 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 17:18 [PATCH RESEND v2 0/3] tpm2-cmd: Improve self test execution Alexander Steffen
[not found] ` <20170831171858.13252-1-Alexander.Steffen-d0qZbvYSIPpWk0Htik3J/w@public.gmane.org>
2017-08-31 17:18 ` [PATCH RESEND v2 1/3] tpm2-cmd: Trigger only missing self tests Alexander Steffen
2017-08-31 17:18 ` [PATCH RESEND v2 2/3] tpm2-cmd: Use dynamic delay to wait for self test result Alexander Steffen
2017-08-31 17:18 ` [PATCH RESEND v2 3/3] tpm2-cmd: React correctly to RC_TESTING from self tests Alexander Steffen
2017-09-02 10:16 ` Jarkko Sakkinen [this message]
2017-09-06 12:57 ` [PATCH RESEND v2 0/3] tpm2-cmd: Improve self test execution Jarkko Sakkinen
2017-09-08 10:00 ` 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=20170902101644.x254cv2jmlw3jruu@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=Alexander.Steffen@infineon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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).