From: Jarkko Sakkinen <jarkko@kernel.org>
To: Stuart Yoder <stuart.yoder@arm.com>
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 v5 1/5] tpm_crb: implement driver compliant to CRB over FF-A
Date: Thu, 20 Feb 2025 11:31:27 +0200 [thread overview]
Message-ID: <Z7b2bwjzWbYE_Qjc@kernel.org> (raw)
In-Reply-To: <Z7b11Kahh7JXDq9E@kernel.org>
On Thu, Feb 20, 2025 at 11:28:58AM +0200, Jarkko Sakkinen wrote:
> On Wed, Feb 19, 2025 at 02:10:10PM -0600, Stuart Yoder wrote:
> > The Arm specification TPM Service CRB over FF-A specification
> > defines the FF-A messages to interact with a CRB-based TPM
> > implemented as an FF-A secure partition.
> >
> > Spec URL:
> > https://developer.arm.com/documentation/den0138/latest/
> >
> > This driver is probed when a TPM Secure Partition is
> > discovered by the FF-A subsystem. It exposes APIs
> > used by the TPM CRB driver to send notifications to
> > the TPM.
> >
> > Acked-by: Sudeep Holla <sudeep.holla@arm.com>
> > Signed-off-by: Stuart Yoder <stuart.yoder@arm.com>
>
> Cutting hairs now but as I cannot test this and this is 1/5:
> can this patch be run without 2/5-4/5?
>
> The policy is that every patch should leave kernel tree to
> a state where it compiles and runs.
The root reason for this is that wrong ordered patch sets
commited to Git add difficulty to bisection in the long-term.
BR, Jarkko
next prev parent reply other threads:[~2025-02-20 9:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 20:10 [PATCH v5 0/5] Add support for the TPM FF-A start method Stuart Yoder
2025-02-19 20:10 ` [PATCH v5 1/5] tpm_crb: implement driver compliant to CRB over FF-A Stuart Yoder
2025-02-20 9:28 ` Jarkko Sakkinen
2025-02-20 9:31 ` Jarkko Sakkinen [this message]
2025-02-20 19:02 ` Stuart Yoder
2025-02-19 20:10 ` [PATCH v5 2/5] tpm_crb: clean-up and refactor check for idle support Stuart Yoder
2025-02-20 9:29 ` Jarkko Sakkinen
2025-02-20 19:04 ` Stuart Yoder
2025-02-20 19:09 ` Paul Menzel
2025-02-20 21:36 ` Jarkko Sakkinen
2025-02-20 21:35 ` Jarkko Sakkinen
2025-02-19 20:10 ` [PATCH v5 3/5] ACPICA: add start method for Arm FF-A Stuart Yoder
2025-02-19 20:10 ` [PATCH v5 4/5] tpm_crb: add support for the Arm FF-A start method Stuart Yoder
2025-02-19 20:10 ` [PATCH v5 5/5] Documentation: tpm: add documentation for the CRB FF-A interface Stuart Yoder
2025-02-20 9:30 ` 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=Z7b2bwjzWbYE_Qjc@kernel.org \
--to=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=stuart.yoder@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.