From: Paul Menzel <pmenzel@molgen.mpg.de>
To: wanghongzhe@huawei.com
Cc: peterhuewe@gmx.de, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org, zhangchenfeng1@huawei.com
Subject: Re: [PATCH] tpm: tpm_tis_spi: set cs_change = 0 when timesout
Date: Tue, 14 Jan 2020 13:12:42 +0100 [thread overview]
Message-ID: <6671d791-e92b-8bfc-0f4f-d80f7e2b2fc2@molgen.mpg.de> (raw)
In-Reply-To: <1579005119-16318-1-git-send-email-wanghongzhe@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
Dear wanghongzhe,
On 2020-01-14 13:31, wanghongzhe wrote:
Your message is from the future (Date: Tue, 14 Jan 2020 20:31:59 +0800).
Please fix your clock. ;-)
Subject: Set cs_change to 0 in case of time-out
> when i reach TPM_RETRY, the cs cannot change back to 'high'.So the TPM chips thinks this communication is not over.
Space after the dot/period.
> And next times communication cannot be effective because the communications mixed up with the last time.
>
> Signed-off-by: wanghongzhe <wanghongzhe@huawei.com>
If you’d configure your name as Wang Hongzhe (or similar) it’d be much
appreciated (`git config --global user.name "Wang …").
[…]
Kind regards,
Paul
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2020-01-14 12:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 12:31 [PATCH] tpm: tpm_tis_spi: set cs_change = 0 when timesout wanghongzhe
2020-01-14 12:12 ` Paul Menzel [this message]
2020-01-14 12:32 ` 答复: " wanghongzhe
-- strict thread matches above, loose matches on Subject: below --
2020-01-15 7:09 [PATCH] tpm:tpm_tis_spi: " wanghongzhe
[not found] <1579071543-22632-1-git-send-email-wanghongzhe@huawei.com>
2020-01-15 6:31 ` wanghongzhe
2020-01-14 12:31 [PATCH] tpm: tpm_tis_spi: " wanghongzhe
2020-01-14 12:12 wanghongzhe
2019-01-15 7:02 [PATCH] tpm:tpm_tis_spi: " wanghongzhe
2019-01-15 6:59 wanghongzhe
2019-01-15 6:56 wanghongzhe
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=6671d791-e92b-8bfc-0f4f-d80f7e2b2fc2@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=wanghongzhe@huawei.com \
--cc=zhangchenfeng1@huawei.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).