From: Petr Vorel <pvorel@suse.cz>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
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] selftests: add TPM 2.0 tests
Date: Sun, 3 Feb 2019 23:26:55 +0100 [thread overview]
Message-ID: <20190203222654.GA28988@x230> (raw)
In-Reply-To: <20190201175054.26105-1-jarkko.sakkinen@linux.intel.com>
Hi Jarkko,
> 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>
> Acked-By: Joey Pabalinas <joeypabalinas@gmail.com>
Reviewed-by: Petr Vorel <petr.vorel@gmail.com>
> +++ b/tools/testing/selftests/tpm2/Makefile
> @@ -0,0 +1,3 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-3-Clause)
> +
> +TEST_PROGS := test_smoke.sh test_space.sh
Maybe include lib.mk, to avoid make No targets error? (well, it's reported for
more tests)
include ../lib.mk
make[1]: Entering directory '/home/pevik/install/src/linux.git/tools/testing/selftests/tpm2'
make[1]: *** No targets. Stop.
Kind regards,
Petr
next prev parent reply other threads:[~2019-02-03 22:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 17:50 [PATCH] selftests: add TPM 2.0 tests Jarkko Sakkinen
2019-02-03 22:26 ` Petr Vorel [this message]
2019-02-04 12:01 ` Jarkko Sakkinen
-- strict thread matches above, loose matches on Subject: below --
2018-11-27 22:10 Jarkko Sakkinen
2018-11-27 22:13 ` Jarkko Sakkinen
2018-11-27 22:34 ` Tadeusz Struk
2018-11-27 23:15 ` Jarkko Sakkinen
2018-11-27 22:49 ` Joey Pabalinas
2018-11-27 22:53 ` Joey Pabalinas
2018-11-27 23:13 ` Jarkko Sakkinen
2018-12-05 0:33 ` Jarkko Sakkinen
2019-01-04 21:09 ` 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=20190203222654.GA28988@x230 \
--to=pvorel@suse.cz \
--cc=PeterHuewe@gmx.de \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--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).