From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
jmorris@namei.org
Cc: linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
Peter Huewe <PeterHuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
Tadeusz Struk <tadeusz.struk@intel.com>
Subject: Re: [PATCH v3] selftests: add TPM 2.0 tests
Date: Tue, 5 Feb 2019 12:13:22 +0200 [thread overview]
Message-ID: <20190205101322.GA31095@linux.intel.com> (raw)
In-Reply-To: <20190204232910.GC14992@linux.intel.com>
On Tue, Feb 05, 2019 at 01:29:10AM +0200, Jarkko Sakkinen wrote:
> On Mon, Feb 04, 2019 at 03:16:40PM +0200, Jarkko Sakkinen wrote:
> > Added the tests that I've been using for testing TPM 2.0 functionality
> > for a long time but have been out-of-tree so far, residing in
> >
> > https://github.com/jsakkine-intel/tpm2-scripts
> >
> > Cc: Tadeusz Struk <tadeusz.struk@intel.com>
> > Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> > Acked-By: Joey Pabalinas <joeypabalinas@gmail.com>
> > Reviewed-by: Petr Vorel <petr.vorel@gmail.com>
>
> Wondering if I can put this to my 5.1 PR?
I'll put it and see what happens. It does not interfere other selftests
anyway and cannot cause compilation errors given that it is pure Python.
/Jarkko
next prev parent reply other threads:[~2019-02-05 10:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 13:16 [PATCH v3] selftests: add TPM 2.0 tests Jarkko Sakkinen
2019-02-04 23:29 ` Jarkko Sakkinen
2019-02-05 10:13 ` Jarkko Sakkinen [this message]
2019-02-05 10:16 ` Jarkko Sakkinen
2019-02-05 20:12 ` James Morris
2019-02-05 20:57 ` 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=20190205101322.GA31095@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=PeterHuewe@gmx.de \
--cc=jgg@ziepe.ca \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=tadeusz.struk@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;
as well as URLs for NNTP newsgroup(s).