From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: linux-kernel@vger.kernel.org, Peter Huewe <peterhuewe@gmx.de>,
Jerry Snitselaar <jsnitsel@redhat.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Philip Tricca <philip.b.tricca@intel.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
linux-integrity@vger.kernel.org,
William Roberts <william.c.roberts@intel.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH] tpm: return a TPM_RC_COMMAND_CODE response if a command isn't implemented
Date: Thu, 7 Dec 2017 12:36:18 +0200 [thread overview]
Message-ID: <20171207103618.2wk37zjh2pxfqxws@linux.intel.com> (raw)
In-Reply-To: <20171207013216.vdyaxcanpmaecx6p@linux.intel.com>
On Thu, Dec 07, 2017 at 03:32:16AM +0200, Jarkko Sakkinen wrote:
> Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
>
> /Jarkko
```
$ python -m unittest -v tpm2_smoke.SpaceTest.test_invalid_cc
test_invalid_cc (tpm2_smoke.SpaceTest) ... ok
----------------------------------------------------------------------
Ran 1 test in 5.833s
OK
``` [1]
Tested-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
/Jarkko
Philip, are you sure you don't want to give tested-by?
[1] https://github.com/jsakkine-intel/tpm2-scripts/commit/4398af02a90442a85751148aebf725992a2949f3
/Jarkko
next prev parent reply other threads:[~2017-12-07 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 23:30 [PATCH] tpm: return a TPM_RC_COMMAND_CODE response if a command isn't implemented Javier Martinez Canillas
2017-11-28 3:21 ` Philip Tricca
2017-11-28 3:32 ` Javier Martinez Canillas
2017-12-07 1:32 ` Jarkko Sakkinen
2017-12-07 8:58 ` Javier Martinez Canillas
2017-12-07 16:10 ` Jarkko Sakkinen
2017-12-07 10:36 ` Jarkko Sakkinen [this message]
2017-12-07 17:56 ` Roberts, William C
2017-12-08 10:50 ` 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=20171207103618.2wk37zjh2pxfqxws@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=javierm@redhat.com \
--cc=jgg@ziepe.ca \
--cc=jgunthorpe@obsidianresearch.com \
--cc=jsnitsel@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=philip.b.tricca@intel.com \
--cc=william.c.roberts@intel.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