From: Jarkko Sakkinen <jarkko@kernel.org>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: Stefan Berger <stefanb@linux.vnet.ibm.com>,
linux-integrity@vger.kernel.org, peterhuewe@gmx.de,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
skhan@linuxfoundation.org
Subject: Re: [PATCH v4 1/2] selftests: tpm2: Determine available PCR bank
Date: Sat, 15 Jan 2022 17:53:18 +0200 [thread overview]
Message-ID: <YeLt7hbm6aIMeWBE@iki.fi> (raw)
In-Reply-To: <1e3b1e6f-6600-d77f-843b-f3d60e062192@linux.ibm.com>
On Thu, Jan 13, 2022 at 01:04:03PM -0500, Stefan Berger wrote:
> Jarkko,
>
> can you take this patch 1/2?
>
> https://lore.kernel.org/lkml/20211128041052.1395504-1-stefanb@linux.vnet.ibm.com/T/#m21209a978c237368499ce5f082f3c0fc03bcbbeb
>
> Stefan
Oops. Sorry, I missed your request at 23rd.
Yes, we can for sure take that. I now tested by with SHA256 only
configuration so:
Tested-by: Jarkko Sakkinen <jarkko@kernel.org>
I'm considering 5.17-rc2 pull rquest but want to leave the final
decision to the time when it can be sent. If I'll make rc2 PR in
the first place, I'll include this to the pull request.
/Jarkko
next prev parent reply other threads:[~2022-01-15 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 4:10 [PATCH v4 0/2] selftests: tpm2: Determine available PCR bank Stefan Berger
2021-11-28 4:10 ` [PATCH v4 1/2] " Stefan Berger
2021-11-29 23:39 ` Jarkko Sakkinen
2021-12-24 1:12 ` Stefan Berger
2022-01-13 18:04 ` Stefan Berger
2022-01-15 15:53 ` Jarkko Sakkinen [this message]
2022-01-15 17:02 ` Jarkko Sakkinen
2021-11-28 4:10 ` [PATCH v4 2/2] selftests: tpm2: Reset the dictionary attack lock Stefan Berger
2021-11-29 23:43 ` Jarkko Sakkinen
2021-11-30 0:26 ` Stefan Berger
2021-12-01 10:16 ` Jarkko Sakkinen
2021-12-01 10:19 ` Jarkko Sakkinen
2021-12-01 14:52 ` Stefan Berger
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=YeLt7hbm6aIMeWBE@iki.fi \
--to=jarkko@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=skhan@linuxfoundation.org \
--cc=stefanb@linux.ibm.com \
--cc=stefanb@linux.vnet.ibm.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