From: Stuart Yoder <stuart.yoder@arm.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: linux-integrity@vger.kernel.org, peterhuewe@gmx.de, jgg@ziepe.ca,
sudeep.holla@arm.com, rafael@kernel.org, lenb@kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] Add support for the TPM FF-A start method
Date: Tue, 11 Feb 2025 17:21:14 -0600 [thread overview]
Message-ID: <b167a781-e9b3-444b-aee2-1c9267f7efeb@arm.com> (raw)
In-Reply-To: <Z6u8DbOlZflmQ9i7@kernel.org>
On 2/11/25 3:07 PM, Jarkko Sakkinen wrote:
> On Mon, Feb 10, 2025 at 05:22:23PM -0600, Stuart Yoder wrote:
>> These patches add support for the CRB FF-A start method defined
>> in the TCG ACPI specification v1.4 and the FF-A ABI defined
>> in the Arm TPM Service CRB over FF-A (DEN0138) specification.
>> (https://developer.arm.com/documentation/den0138/latest/)
>
>
> It would bring a whole a lot of clarity to open up acronyms.
> What are F, F and A? There's quite a few of these in this
> industry.
>
> Also, probably you could take the spec out of parentheses and
> use double colon.
Will do this in v2.
Stuart
prev parent reply other threads:[~2025-02-11 23:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 23:22 [PATCH 0/4] Add support for the TPM FF-A start method Stuart Yoder
2025-02-10 23:22 ` [PATCH 1/4] tpm_crb: implement driver compliant to CRB over FF-A Stuart Yoder
2025-02-11 21:08 ` Jarkko Sakkinen
2025-02-11 23:21 ` Stuart Yoder
2025-02-10 23:22 ` [PATCH 2/4] tpm_crb: refactor check for idle support into TPM into inline function Stuart Yoder
2025-02-10 23:22 ` [PATCH 3/4] ACPICA: add start method for Arm FF-A Stuart Yoder
2025-02-11 9:57 ` Sudeep Holla
2025-02-11 21:50 ` Stuart Yoder
2025-02-10 23:22 ` [PATCH 4/4] tpm_crb: add support for the Arm FF-A start method Stuart Yoder
2025-02-11 6:45 ` [PATCH 0/4] Add support for the TPM " Sumit Garg
2025-02-11 16:09 ` Stuart Yoder
2025-02-12 7:39 ` Sumit Garg
2025-02-12 21:55 ` Stuart Yoder
2025-02-13 5:31 ` Sumit Garg
2025-02-13 15:19 ` Stuart Yoder
2025-02-17 5:17 ` Sumit Garg
2025-02-17 16:56 ` Stuart Yoder
2025-02-21 13:46 ` Sumit Garg
2025-02-21 14:02 ` Sudeep Holla
2025-02-21 18:29 ` Stuart Yoder
2025-02-22 15:39 ` Sudeep Holla
2025-02-11 10:12 ` Sudeep Holla
2025-02-11 21:07 ` Jarkko Sakkinen
2025-02-11 23:21 ` Stuart Yoder [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=b167a781-e9b3-444b-aee2-1c9267f7efeb@arm.com \
--to=stuart.yoder@arm.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.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