From: Nayna <nayna@linux.vnet.ibm.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>,
linux-integrity@vger.kernel.org
Cc: aik@ozlabs.ru, david@gibson.dropbear.id.au,
linux-kernel@vger.kernel.org, gcwilson@linux.ibm.com,
Stefan Berger <stefanb@linux.ibm.com>
Subject: Re: [PATCH 2/3] tpm: ibmvtpm: Wait for buffer to be set before proceeding
Date: Thu, 13 Feb 2020 12:53:50 -0500 [thread overview]
Message-ID: <568c8b9b-31e1-c6eb-c88b-12e8cf731473@linux.vnet.ibm.com> (raw)
In-Reply-To: <20200204132706.3220416-3-stefanb@linux.vnet.ibm.com>
On 2/4/20 8:27 AM, Stefan Berger wrote:
> From: Stefan Berger <stefanb@linux.ibm.com>
>
> Synchronize with the results from the CRQs before continuing with
> the initialization. This avoids trying to send TPM commands while
> the rtce buffer has not been allocated, yet.
Seems like it is not specific to vtpm 2.0. Shall it be clarified that
it is a fix for vtpm 1.2 also ?
Thanks & Regards,
- Nayna
next prev parent reply other threads:[~2020-02-13 17:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 13:27 [PATCH 0/3] Enable vTPM 2.0 for the IBM vTPM driver Stefan Berger
2020-02-04 13:27 ` [PATCH 1/3] tpm: of: Handle IBM,vtpm20 case when getting log parameters Stefan Berger
2020-02-13 17:46 ` Nayna
2020-02-13 19:16 ` Stefan Berger
2020-03-11 12:01 ` Stefan Berger
2020-02-04 13:27 ` [PATCH 2/3] tpm: ibmvtpm: Wait for buffer to be set before proceeding Stefan Berger
2020-02-13 17:53 ` Nayna [this message]
2020-02-13 18:11 ` Stefan Berger
2020-02-04 13:27 ` [PATCH 3/3] tpm: ibmvtpm: Add support for TPM 2 Stefan Berger
2020-02-13 17:53 ` Nayna
2020-02-13 18:20 ` Stefan Berger
2020-02-13 18:35 ` Jason Gunthorpe
2020-02-13 19:04 ` Stefan Berger
2020-02-13 19:11 ` Jason Gunthorpe
2020-02-13 19:15 ` Stefan Berger
2020-02-13 19:39 ` Jason Gunthorpe
2020-02-13 19:45 ` Stefan Berger
2020-02-13 19:50 ` Jason Gunthorpe
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=568c8b9b-31e1-c6eb-c88b-12e8cf731473@linux.vnet.ibm.com \
--to=nayna@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=gcwilson@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).