linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
To: Peter.Huewe@infineon.com, arnd@arndb.de
Cc: peterhuewe@gmx.de, jarkko.sakkinen@linux.intel.com, jgg@ziepe.ca,
	gregkh@linuxfoundation.org, linux-integrity@vger.kernel.org,
	linux-kernel@vger.kernel.org, christophe.ricard@gmail.com,
	Alexander.Steffen@infineon.com
Subject: Re: [PATCH] tpm: Fix the description error of the help information in Kconfig
Date: Tue, 28 Jul 2020 20:32:45 +0800	[thread overview]
Message-ID: <21de5951-c2d3-a7fb-683e-9d18fc59d8ae@linux.alibaba.com> (raw)
In-Reply-To: <09571889ac784850a6c5855f2dc0888e@infineon.com>


On 2020/7/27 16:33, Peter.Huewe@infineon.com wrote:
> Hi,
> On 2020/7/27 15:10, Arnd Bergmann wrote:
>> On Mon, Jul 27, 2020 at 4:54 AM Tianjia Zhang
>> <tianjia.zhang@linux.alibaba.com> wrote:
>>>
>>> Obviously, the TPM version number in the help message is wrong, which
>>> will cause confusion. This patch fixes it.
>>
>> How is this "obvious"? I tried finding the specification and could not
>> see anything to back up TIS 1.3 being only supported with TPM 1.3, or
>> the existence of a TPM 1.3 specification at all.
>>
> There is no TPM 1.3.
> 
> There is a TIS Specification 1.3 which applies to TPM1.2
> These are different specs, with different version numbers.
> So the fix is incorrect.
> 
> Thanks,
> Peter
> 

You are right, I was careless, thanks for your reply.

Thanks and best,
Tianjia

      reply	other threads:[~2020-07-28 12:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27  2:53 [PATCH] tpm: Fix the description error of the help information in Kconfig Tianjia Zhang
2020-07-27  7:10 ` Arnd Bergmann
2020-07-27  8:25   ` Tianjia Zhang
2020-07-27  8:33     ` Peter.Huewe
2020-07-28 12:32       ` Tianjia Zhang [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=21de5951-c2d3-a7fb-683e-9d18fc59d8ae@linux.alibaba.com \
    --to=tianjia.zhang@linux.alibaba.com \
    --cc=Alexander.Steffen@infineon.com \
    --cc=Peter.Huewe@infineon.com \
    --cc=arnd@arndb.de \
    --cc=christophe.ricard@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    /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).