[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6ab9e1f1f59c4f5ba04570bc870515aa@huawei.com>
Date: Tue, 14 Jan 2020 12:32:38 +0000
From: wanghongzhe <wanghongzhe@...wei.com>
To: Paul Menzel <pmenzel@...gen.mpg.de>
CC: "peterhuewe@....de" <peterhuewe@....de>,
"linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Zhangchenfeng (EulerOS)" <zhangchenfeng1@...wei.com>
Subject: 答复: [PATCH] tpm: tpm_tis_spi: set cs_change = 0 when timesout
Sorry, I have change these mistakes in another emails
-----邮件原件-----
发件人: Paul Menzel [mailto:pmenzel@...gen.mpg.de]
发送时间: 2020年1月14日 20:13
收件人: wanghongzhe <wanghongzhe@...wei.com>
抄送: peterhuewe@....de; linux-integrity@...r.kernel.org; linux-kernel@...r.kernel.org; Zhangchenfeng (EulerOS) <zhangchenfeng1@...wei.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@...wei.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
Powered by blists - more mailing lists