From: Jarkko Sakkinen <jarkko@kernel.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>, 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 2/5] tpm_crb: clean-up and refactor check for idle support
Date: Thu, 20 Feb 2025 23:36:22 +0200 [thread overview]
Message-ID: <0d8682ca28d2ed43d1d0f1b2a28f7d62e4ee2957.camel@kernel.org> (raw)
In-Reply-To: <285e81d8-dd07-4075-9c09-0e2b4e59aeae@molgen.mpg.de>
On Thu, 2025-02-20 at 20:09 +0100, Paul Menzel wrote:
> Dear Stuart,
>
>
> Thank you for the patch. Should you respin, you could spell *clean
> up*
> in the summary/title with a space.
>
> The diff looks good.
>
>
> Kind regards,
>
> Paul
So for the sake of overall good it is better maybe to keep
this immutable as this will make it more plausible for
potential testers.
BR, Jarkko
next prev parent reply other threads:[~2025-02-20 21:36 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
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 [this message]
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=0d8682ca28d2ed43d1d0f1b2a28f7d62e4ee2957.camel@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=pmenzel@molgen.mpg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®