From: Jarkko Sakkinen <jarkko@kernel.org>
To: Florian Eckert <fe@dev.tdt.de>,
peterhuewe@gmx.de, jgg@ziepe.ca, Eckert.Florian@googlemail.com
Cc: linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] tpm/tpm_i2c_infineon: Fix init endian vendor check
Date: Mon, 13 Sep 2021 23:31:13 +0300 [thread overview]
Message-ID: <169a507329c2273f64c1c7ebab0a3530b19e971e.camel@kernel.org> (raw)
In-Reply-To: <20210913120521.18572-1-fe@dev.tdt.de>
On Mon, 2021-09-13 at 14:05 +0200, Florian Eckert wrote:
> On my embedded system I use this tpm infineon chip via i2c bus.
> The system is a MIPS architecture and therefore works in big endian mode.
>
> The problem is, that the chip type is not correctly recognized,
> because the vendor ID is wrongly aligned in the memory.
>
> By declaring the vendor ID variable as a `__le32` type, the TPM chip is
> then correctly recognized by the driver and feels then responsible.
Please no hyphens just normal single quotes.
You should have always in a commit message some explanation what
the patch does in imperative form, e.g. "Change type of xxx ...
because ...".
I cannot from find a variable named "vendor ID" from
tpm_tis_i2c_init(). Maybe you are referring to the variable,
of which name is "vendor"?
Finally, the commit message lacks explanation what is changed, i.e.
tpm2_tis_i2c_init() in this case.
Did you find the commit ID where this regression was introduceD?
/Jarkko
prev parent reply other threads:[~2021-09-13 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 12:05 [PATCH v2 1/1] tpm/tpm_i2c_infineon: Fix init endian vendor check Florian Eckert
2021-09-13 13:02 ` Jason Gunthorpe
2021-09-13 13:46 ` Florian Eckert
2021-09-13 14:03 ` Jason Gunthorpe
2021-09-13 18:31 ` kernel test robot
2021-09-13 20:31 ` Jarkko Sakkinen [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=169a507329c2273f64c1c7ebab0a3530b19e971e.camel@kernel.org \
--to=jarkko@kernel.org \
--cc=Eckert.Florian@googlemail.com \
--cc=fe@dev.tdt.de \
--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