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:16:42 +0200 [thread overview]
Message-ID: <20190205101642.GA27954@linux.intel.com> (raw)
In-Reply-To: <20190205101322.GA31095@linux.intel.com>
On Tue, Feb 05, 2019 at 12:13:22PM +0200, Jarkko Sakkinen wrote:
> 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.
Applied to git://git.infradead.org/users/jjs/linux-tpmdd.git.
Will be part of my next PR to James' security tree.
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: jarkko.sakkinen at linux.intel.com (Jarkko Sakkinen)
Subject: [PATCH v3] selftests: add TPM 2.0 tests
Date: Tue, 5 Feb 2019 12:16:42 +0200 [thread overview]
Message-ID: <20190205101642.GA27954@linux.intel.com> (raw)
In-Reply-To: <20190205101322.GA31095@linux.intel.com>
On Tue, Feb 05, 2019 at 12:13:22PM +0200, Jarkko Sakkinen wrote:
> 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 at intel.com>
> > > Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen at linux.intel.com>
> > > Acked-By: Joey Pabalinas <joeypabalinas at gmail.com>
> > > Reviewed-by: Petr Vorel <petr.vorel at 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.
Applied to git://git.infradead.org/users/jjs/linux-tpmdd.git.
Will be part of my next PR to James' security tree.
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: jarkko.sakkinen@linux.intel.com (Jarkko Sakkinen)
Subject: [PATCH v3] selftests: add TPM 2.0 tests
Date: Tue, 5 Feb 2019 12:16:42 +0200 [thread overview]
Message-ID: <20190205101642.GA27954@linux.intel.com> (raw)
Message-ID: <20190205101642.BJcRo7SZ2Qsowv62L-y-s6n7wsxpVFrNnJSsJEds4Xo@z> (raw)
In-Reply-To: <20190205101322.GA31095@linux.intel.com>
On Tue, Feb 05, 2019@12:13:22PM +0200, Jarkko Sakkinen wrote:
> On Tue, Feb 05, 2019@01:29:10AM +0200, Jarkko Sakkinen wrote:
> > On Mon, Feb 04, 2019@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 at intel.com>
> > > Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen at linux.intel.com>
> > > Acked-By: Joey Pabalinas <joeypabalinas at gmail.com>
> > > Reviewed-by: Petr Vorel <petr.vorel at 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.
Applied to git://git.infradead.org/users/jjs/linux-tpmdd.git.
Will be part of my next PR to James' security tree.
/Jarkko
next prev parent reply other threads:[~2019-02-05 10:16 UTC|newest]
Thread overview: 22+ 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 13:16 ` Jarkko Sakkinen
2019-02-04 13:16 ` jarkko.sakkinen
2019-02-04 23:29 ` Jarkko Sakkinen
2019-02-04 23:29 ` Jarkko Sakkinen
2019-02-04 23:29 ` jarkko.sakkinen
2019-02-05 10:13 ` Jarkko Sakkinen
2019-02-05 10:13 ` Jarkko Sakkinen
2019-02-05 10:13 ` jarkko.sakkinen
2019-02-05 10:16 ` Jarkko Sakkinen [this message]
2019-02-05 10:16 ` Jarkko Sakkinen
2019-02-05 10:16 ` jarkko.sakkinen
2019-02-05 20:12 ` James Morris
2019-02-05 20:12 ` James Morris
2019-02-05 20:12 ` jmorris
2019-02-05 20:57 ` Jarkko Sakkinen
2019-02-05 20:57 ` Jarkko Sakkinen
2019-02-05 20:57 ` jarkko.sakkinen
2019-02-18 2:16 ` [LKP] [selftests] 60b119cae8: kernel_selftests.tpm2.test_smoke.sh.fail kernel test robot
2019-02-18 2:16 ` kernel test robot
2019-02-18 13:55 ` [LKP] " Jarkko Sakkinen
2019-02-18 13:55 ` 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=20190205101642.GA27954@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 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.