From: Tadeusz Struk <tstruk@gmail.com>
To: Jarkko Sakkinen <jarkko@kernel.org>,
Tadeusz Struk <tadeusz.struk@linaro.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
linux-integrity@vger.kernel.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org, stefanb@linux.ibm.com
Subject: Re: [PATCH v3 1/2] tpm: Fix error handling in async work
Date: Sat, 15 Jan 2022 17:22:58 -0800 [thread overview]
Message-ID: <7a94d9a3-729a-817a-d2bc-143c25a2a5d4@gmail.com> (raw)
In-Reply-To: <YeHnTlK+QCZiUyOL@iki.fi>
On 1/14/22 13:12, Jarkko Sakkinen wrote:
>> Please send new versions, there's also this:
>>
>> def test_flush_invlid_context()
>>
>> I'd figure "invlid" should be "invalid"
>>
>> You can add, as these changes do not change the semantics of the
>> patches:
>>
>> Tested-by: Jarkko Sakkinen<jarkko@kernel.org>
>>
>> It's always best if you author the final version, as then a clear
>> reference on what was accepted exist at lore.kernel.org.
> Maybe it is good to mention that the test environment was libvirt hosted
> QEMU using swtpm, which I tried for the first time, instead of real hadware
> (libvirt has a nice property that it handles the startup/shutdown of
> swtpm). I managed to run all tests so I guess swtpm is working properly.
Yes, I have been using it all the time for testing since the support was
added to qemu. New versions on their way.
Thanks,
Tadeusz
prev parent reply other threads:[~2022-01-16 1:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 5:52 Tadeusz Struk
2022-01-11 5:52 ` [PATCH v2 2/2] selftests: tpm: add async space test with noneexisting handle Tadeusz Struk
2022-01-12 18:35 ` [PATCH v3 1/2] tpm: Fix error handling in async work Jarkko Sakkinen
2022-01-12 18:47 ` Tadeusz Struk
2022-01-14 21:07 ` Jarkko Sakkinen
2022-01-14 21:12 ` Jarkko Sakkinen
2022-01-16 1:22 ` Tadeusz Struk [this message]
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=7a94d9a3-729a-817a-d2bc-143c25a2a5d4@gmail.com \
--to=tstruk@gmail.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=stefanb@linux.ibm.com \
--cc=tadeusz.struk@linaro.org \
/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
all inboxes | Powered by JetHome®