netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Jakub Kicinski" <kuba@kernel.org>
Cc: <linux-integrity@vger.kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Daniel P . Smith" <dpsmith@apertussolutions.com>,
	"Lino Sanfilippo" <l.sanfilippo@kunbus.com>,
	"Jason Gunthorpe" <jgg@ziepe.ca>,
	"Peter Huewe" <peterhuewe@gmx.de>,
	"James Bottomley" <James.Bottomley@HansenPartnership.com>,
	"Alexander Steffen" <Alexander.Steffen@infineon.com>,
	<keyrings@vger.kernel.org>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Richard Cochran" <richardcochran@gmail.com>,
	"open list:PTP HARDWARE CLOCK SUPPORT:Keyword:(?:b|_)ptp(?:b|_)"
	<netdev@vger.kernel.org>
Subject: Re: [PATCH v4] Documentation: tpm_tis
Date: Sat, 23 Mar 2024 20:25:41 +0200	[thread overview]
Message-ID: <D01C9XMYRA1M.N94CPODMQSXS@kernel.org> (raw)
In-Reply-To: <20240322155233.30422299@kernel.org>

On Sat Mar 23, 2024 at 12:52 AM EET, Jakub Kicinski wrote:
> On Fri, 22 Mar 2024 14:35:36 +0200 Jarkko Sakkinen wrote:
> > +TCG PTP Specification defines two interface types: FIFO and CRB. The former is
>
> Could be worth spelling out the PTP part here, I'm guessing
> get_maintainer made you CC netdev because it thought it stands
> for Precision Time Protocol. And one has to read till the end
> to see:
>
> > +TCG PC Client Platform TPM Profile (PTP) Specification

Thanks! Good remark.

BR, Jarkko

  reply	other threads:[~2024-03-23 18:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 12:35 [PATCH v4] Documentation: tpm_tis Jarkko Sakkinen
2024-03-22 22:52 ` Jakub Kicinski
2024-03-23 18:25   ` Jarkko Sakkinen [this message]
2024-03-23  0:39 ` Daniel P. Smith
2024-03-23 18:40   ` Jarkko Sakkinen
2024-03-24  2:14     ` Jarkko Sakkinen

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=D01C9XMYRA1M.N94CPODMQSXS@kernel.org \
    --to=jarkko@kernel.org \
    --cc=Alexander.Steffen@infineon.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=corbet@lwn.net \
    --cc=dpsmith@apertussolutions.com \
    --cc=jgg@ziepe.ca \
    --cc=keyrings@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=l.sanfilippo@kunbus.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=rdunlap@infradead.org \
    --cc=richardcochran@gmail.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;
as well as URLs for NNTP newsgroup(s).