From: wanghongzhe <wanghongzhe@huawei.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: "peterhuewe@gmx.de" <peterhuewe@gmx.de>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Zhangchenfeng (EulerOS)" <zhangchenfeng1@huawei.com>
Subject: 答复: [PATCH] tpm: tpm_tis_spi: set cs_change = 0 when timesout
Date: Tue, 14 Jan 2020 12:32:38 +0000 [thread overview]
Message-ID: <6ab9e1f1f59c4f5ba04570bc870515aa@huawei.com> (raw)
In-Reply-To: <6671d791-e92b-8bfc-0f4f-d80f7e2b2fc2@molgen.mpg.de>
Sorry, I have change these mistakes in another emails
-----邮件原件-----
发件人: Paul Menzel [mailto:pmenzel@molgen.mpg.de]
发送时间: 2020年1月14日 20:13
收件人: wanghongzhe <wanghongzhe@huawei.com>
抄送: peterhuewe@gmx.de; linux-integrity@vger.kernel.org; linux-kernel@vger.kernel.org; Zhangchenfeng (EulerOS) <zhangchenfeng1@huawei.com>
主题: Re: [PATCH] tpm: tpm_tis_spi: set cs_change = 0 when timesout
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
prev parent reply other threads:[~2020-01-14 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 12:31 wanghongzhe
2020-01-14 12:12 ` Paul Menzel
2020-01-14 12:32 ` wanghongzhe [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=6ab9e1f1f59c4f5ba04570bc870515aa@huawei.com \
--to=wanghongzhe@huawei.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=pmenzel@molgen.mpg.de \
--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
all inboxes | Powered by JetHome®