From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Marek Vasut" <marex@denx.de>, <devicetree@vger.kernel.org>
Cc: "Conor Dooley" <conor+dt@kernel.org>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Lukas Wunner" <lukas@wunner.de>,
"Peter Huewe" <peterhuewe@gmx.de>,
"Rob Herring" <robh@kernel.org>,
<linux-integrity@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: tpm: Add st,st33tphf2ei2c
Date: Fri, 27 Dec 2024 07:24:49 +0200 [thread overview]
Message-ID: <D6M8E1PL27QI.21DRRGR1MN8KR@kernel.org> (raw)
In-Reply-To: <38ac27d2-6c79-452c-8f8d-d55f05519d05@denx.de>
On Thu Dec 26, 2024 at 10:29 PM EET, Marek Vasut wrote:
> On 12/26/24 8:54 PM, Jarkko Sakkinen wrote:
> > On Thu Dec 26, 2024 at 7:10 PM EET, Marek Vasut wrote:
> >> Add the ST chip st33tphf2ei2c to the supported compatible strings of the
> >> TPM TIS I2C schema. The Chip is compliant with the TCG PC Client TPM
> > ~~~~
> > chip
>
> Fixed, thanks.
>
> >> Profile specification.
> >>
> >> For reference, a databrief is available at:
> >> https://www.st.com/resource/en/data_brief/st33tphf2ei2c.pdf
> >
> > Or just this would be enough:
> >
> > Link: https://www.st.com/resource/en/data_brief/st33tphf2ei2c.pdf
> I don't think Link: tag should be used for datasheets and other such
> stuff, my understanding of the Link: tag is that it is used to point to
> the patch at lore.k.o once applied ?
Oh, you are right and I did not know this :-) I've never read this page
before (ever) because I did not know it was necessary:
https://www.kernel.org/doc/html/latest/maintainer/configure-git.html
So I've used up until today link-tag for links... I just thought that
"well, I have Git configured"...
BR, Jarkko
next prev parent reply other threads:[~2024-12-27 5:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 17:10 [PATCH] dt-bindings: tpm: Add st,st33tphf2ei2c Marek Vasut
2024-12-26 19:54 ` Jarkko Sakkinen
2024-12-26 20:29 ` Marek Vasut
2024-12-27 5:24 ` Jarkko Sakkinen [this message]
2024-12-27 7:00 ` Krzysztof Kozlowski
2024-12-27 15:00 ` Marek Vasut
2024-12-28 10:32 ` Krzysztof Kozlowski
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=D6M8E1PL27QI.21DRRGR1MN8KR@kernel.org \
--to=jarkko@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jgg@ziepe.ca \
--cc=krzk+dt@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=marex@denx.de \
--cc=peterhuewe@gmx.de \
--cc=robh@kernel.org \
/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