From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Tadeusz Struk <tadeusz.struk@intel.com>
Cc: linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
Shuah Khan <shuah@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH] selftests: add TPM 2.0 tests
Date: Tue, 27 Nov 2018 15:15:39 -0800 [thread overview]
Message-ID: <20181127231539.GC26051@linux.intel.com> (raw)
In-Reply-To: <0929dfe2-83aa-ff39-e37e-35bc499aaa0a@intel.com>
On Tue, Nov 27, 2018 at 02:34:39PM -0800, Tadeusz Struk wrote:
> On 11/27/18 2:10 PM, Jarkko Sakkinen wrote:
> > Added the tests that I've been using for testing TPM 2.0 functionality
> > for long time but have 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>
> > ---
> > Tadeusz: does not include your test. Better that you send them after
> > this has been accepted to get proper SOB info.
>
> Sure I can follow up after this is merged.
> Thanks,
Hey, noticed that there was extra parentheses in open() for tpmrm0. Not
a biggie, I fixed it in my tpm2-scripts tree, but when you actually go
on to make the commit and send it here for review run both test_smoke.sh
and test_space.sh.
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: jarkko.sakkinen at linux.intel.com (Jarkko Sakkinen)
Subject: [PATCH] selftests: add TPM 2.0 tests
Date: Tue, 27 Nov 2018 15:15:39 -0800 [thread overview]
Message-ID: <20181127231539.GC26051@linux.intel.com> (raw)
In-Reply-To: <0929dfe2-83aa-ff39-e37e-35bc499aaa0a@intel.com>
On Tue, Nov 27, 2018 at 02:34:39PM -0800, Tadeusz Struk wrote:
> On 11/27/18 2:10 PM, Jarkko Sakkinen wrote:
> > Added the tests that I've been using for testing TPM 2.0 functionality
> > for long time but have out-of-tree so far residing in
> >
> > https://github.com/jsakkine-intel/tpm2-scripts
> >
> > Cc: Tadeusz Struk <tadeusz.struk at intel.com>
> > Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen at linux.intel.com>
> > ---
> > Tadeusz: does not include your test. Better that you send them after
> > this has been accepted to get proper SOB info.
>
> Sure I can follow up after this is merged.
> Thanks,
Hey, noticed that there was extra parentheses in open() for tpmrm0. Not
a biggie, I fixed it in my tpm2-scripts tree, but when you actually go
on to make the commit and send it here for review run both test_smoke.sh
and test_space.sh.
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: jarkko.sakkinen@linux.intel.com (Jarkko Sakkinen)
Subject: [PATCH] selftests: add TPM 2.0 tests
Date: Tue, 27 Nov 2018 15:15:39 -0800 [thread overview]
Message-ID: <20181127231539.GC26051@linux.intel.com> (raw)
Message-ID: <20181127231539.m_b-gFU9kH7QSASQFkcjhO5cbEs7lXqpsJIZQj1N_7E@z> (raw)
In-Reply-To: <0929dfe2-83aa-ff39-e37e-35bc499aaa0a@intel.com>
On Tue, Nov 27, 2018@02:34:39PM -0800, Tadeusz Struk wrote:
> On 11/27/18 2:10 PM, Jarkko Sakkinen wrote:
> > Added the tests that I've been using for testing TPM 2.0 functionality
> > for long time but have out-of-tree so far residing in
> >
> > https://github.com/jsakkine-intel/tpm2-scripts
> >
> > Cc: Tadeusz Struk <tadeusz.struk at intel.com>
> > Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen at linux.intel.com>
> > ---
> > Tadeusz: does not include your test. Better that you send them after
> > this has been accepted to get proper SOB info.
>
> Sure I can follow up after this is merged.
> Thanks,
Hey, noticed that there was extra parentheses in open() for tpmrm0. Not
a biggie, I fixed it in my tpm2-scripts tree, but when you actually go
on to make the commit and send it here for review run both test_smoke.sh
and test_space.sh.
/Jarkko
next prev parent reply other threads:[~2018-11-27 23:15 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 22:10 [PATCH] selftests: add TPM 2.0 tests Jarkko Sakkinen
2018-11-27 22:10 ` Jarkko Sakkinen
2018-11-27 22:10 ` jarkko.sakkinen
2018-11-27 22:13 ` Jarkko Sakkinen
2018-11-27 22:13 ` Jarkko Sakkinen
2018-11-27 22:13 ` jarkko.sakkinen
2018-11-27 22:34 ` Tadeusz Struk
2018-11-27 22:34 ` Tadeusz Struk
2018-11-27 22:34 ` tadeusz.struk
2018-11-27 23:15 ` Jarkko Sakkinen [this message]
2018-11-27 23:15 ` Jarkko Sakkinen
2018-11-27 23:15 ` jarkko.sakkinen
2018-11-27 22:49 ` Joey Pabalinas
2018-11-27 22:49 ` Joey Pabalinas
2018-11-27 22:49 ` joeypabalinas
2018-11-27 22:53 ` Joey Pabalinas
2018-11-27 22:53 ` Joey Pabalinas
2018-11-27 22:53 ` joeypabalinas
2018-11-27 23:13 ` Jarkko Sakkinen
2018-11-27 23:13 ` Jarkko Sakkinen
2018-11-27 23:13 ` jarkko.sakkinen
2018-12-05 0:33 ` Jarkko Sakkinen
2018-12-05 0:33 ` Jarkko Sakkinen
2018-12-05 0:33 ` jarkko.sakkinen
2019-01-04 21:09 ` Jarkko Sakkinen
2019-01-04 21:09 ` Jarkko Sakkinen
2019-01-04 21:09 ` jarkko.sakkinen
-- strict thread matches above, loose matches on Subject: below --
2019-02-01 17:50 Jarkko Sakkinen
2019-02-01 17:50 ` Jarkko Sakkinen
2019-02-01 17:50 ` jarkko.sakkinen
2019-02-03 22:26 ` Petr Vorel
2019-02-03 22:26 ` Petr Vorel
2019-02-03 22:26 ` pvorel
2019-02-04 12:01 ` Jarkko Sakkinen
2019-02-04 12:01 ` Jarkko Sakkinen
2019-02-04 12:01 ` 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=20181127231539.GC26051@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.