From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Tadeusz Struk <tadeusz.struk@intel.com>
Cc: linux-kselftest@vger.kernel.org, shuah@kernel.org,
linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org, PeterHuewe@gmx.de,
jgg@ziepe.ca
Subject: Re: [PATCH v3] selftests/tpm2: Extend tests to cover partial reads
Date: Wed, 13 Feb 2019 20:07:59 +0200 [thread overview]
Message-ID: <20190213180759.GB27173@linux.intel.com> (raw)
In-Reply-To: <24290564-9c4d-93f4-d813-7ce4f1fd8745@intel.com>
On Wed, Feb 13, 2019 at 09:22:56AM -0800, Tadeusz Struk wrote:
> On 2/13/19 9:19 AM, Jarkko Sakkinen wrote:
> > OK, great, thank you.
> >
> > They are in my master branch now.
>
> Thanks Jarkko. Are you planning to push it also to 5.1?
I did already my v5.1 pull request but might do another one if there are
regressions. So it depends.
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: jarkko.sakkinen at linux.intel.com (Jarkko Sakkinen)
Subject: [PATCH v3] selftests/tpm2: Extend tests to cover partial reads
Date: Wed, 13 Feb 2019 20:07:59 +0200 [thread overview]
Message-ID: <20190213180759.GB27173@linux.intel.com> (raw)
In-Reply-To: <24290564-9c4d-93f4-d813-7ce4f1fd8745@intel.com>
On Wed, Feb 13, 2019 at 09:22:56AM -0800, Tadeusz Struk wrote:
> On 2/13/19 9:19 AM, Jarkko Sakkinen wrote:
> > OK, great, thank you.
> >
> > They are in my master branch now.
>
> Thanks Jarkko. Are you planning to push it also to 5.1?
I did already my v5.1 pull request but might do another one if there are
regressions. So it depends.
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: jarkko.sakkinen@linux.intel.com (Jarkko Sakkinen)
Subject: [PATCH v3] selftests/tpm2: Extend tests to cover partial reads
Date: Wed, 13 Feb 2019 20:07:59 +0200 [thread overview]
Message-ID: <20190213180759.GB27173@linux.intel.com> (raw)
Message-ID: <20190213180759.F_dwub115QwILYNTSGUzk47sKY6JYmKnukUtiHrMIbo@z> (raw)
In-Reply-To: <24290564-9c4d-93f4-d813-7ce4f1fd8745@intel.com>
On Wed, Feb 13, 2019@09:22:56AM -0800, Tadeusz Struk wrote:
> On 2/13/19 9:19 AM, Jarkko Sakkinen wrote:
> > OK, great, thank you.
> >
> > They are in my master branch now.
>
> Thanks Jarkko. Are you planning to push it also to 5.1?
I did already my v5.1 pull request but might do another one if there are
regressions. So it depends.
/Jarkko
next prev parent reply other threads:[~2019-02-13 18:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 16:39 [PATCH v2] selftests/tpm2: Open tpm dev in unbuffered mode Tadeusz Struk
2019-02-13 16:39 ` Tadeusz Struk
2019-02-13 16:39 ` tadeusz.struk
2019-02-13 16:40 ` [PATCH v3] selftests/tpm2: Extend tests to cover partial reads Tadeusz Struk
2019-02-13 16:40 ` Tadeusz Struk
2019-02-13 16:40 ` tadeusz.struk
2019-02-13 17:19 ` Jarkko Sakkinen
2019-02-13 17:19 ` Jarkko Sakkinen
2019-02-13 17:19 ` jarkko.sakkinen
2019-02-13 17:22 ` Tadeusz Struk
2019-02-13 17:22 ` Tadeusz Struk
2019-02-13 17:22 ` tadeusz.struk
2019-02-13 18:07 ` Jarkko Sakkinen [this message]
2019-02-13 18:07 ` Jarkko Sakkinen
2019-02-13 18:07 ` 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=20190213180759.GB27173@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=PeterHuewe@gmx.de \
--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 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.