linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Alexander Steffen <Alexander.Steffen@infineon.com>
Cc: linux-integrity@vger.kernel.org
Subject: Re: [PATCH] tpm: fix selftest failure regression
Date: Tue, 20 Feb 2018 16:24:06 +0200	[thread overview]
Message-ID: <1519136646.4113.13.camel@linux.intel.com> (raw)
In-Reply-To: <1518810337.4475.16.camel@HansenPartnership.com>

On Fri, 2018-02-16 at 11:45 -0800, James Bottomley wrote:
> tsscreateek -cp -alg ec -noflush

Can you describe in high-level what this command does? I will rather
add a test to my smoke test suite than depend on TSS implementations
for various reasons. This seems like a good test case to add as
part of it.

/Jarkko

  reply	other threads:[~2018-02-20 14:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1518122886.21828.20.camel@HansenPartnership.com>
2018-02-15 13:55 ` [PATCH] tpm: fix selftest failure regression Jarkko Sakkinen
2018-02-16  8:34 ` Jarkko Sakkinen
2018-02-16 18:17   ` James Bottomley
2018-02-16 18:59     ` James Bottomley
2018-02-16 19:26       ` Alexander Steffen
2018-02-16 19:45         ` James Bottomley
2018-02-20 14:24           ` Jarkko Sakkinen [this message]
2018-02-20 14:33             ` James Bottomley
2018-04-08 19:11             ` Ken Goldman
2018-02-20 13:30     ` Jarkko Sakkinen
2018-02-20 13:57       ` James Bottomley
2018-02-20 17:22         ` Jarkko Sakkinen
2018-02-20 17:27           ` James Bottomley
2018-02-16 20:15   ` James Bottomley
2018-02-18 17:08     ` Jason Gunthorpe
2018-02-18 17:16       ` James Bottomley
2018-02-18 17:36         ` Jason Gunthorpe
2018-02-18 18:06           ` James Bottomley
2018-02-20 14:25     ` 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=1519136646.4113.13.camel@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=Alexander.Steffen@infineon.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-integrity@vger.kernel.org \
    /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).