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 v3 1/5] tpm_crb: implement driver compliant to CRB over FF-A
Date: Mon, 17 Feb 2025 17:59:41 +0200 [thread overview]
Message-ID: <Z7Nc7Rs_bny6Bkyn@kernel.org> (raw)
In-Reply-To: <195bc518-a20a-487f-b1ad-e83ca9ed5630@arm.com>
On Mon, Feb 17, 2025 at 09:53:24AM -0600, Stuart Yoder wrote:
> > You probably did not run checkpatch.pl with '--strict', did you? ;-)
>
> No, did no check with --strict. Will do that.
Not blaming you :-) I learned it like a year or two ago randomly.
It's very useful option that gives much more deeper information
about various issues.
That said, no need to hit yourself to the wall with it. Sometimes
it also gives errors that are by practical means unreasonable to
resolve.
BR, Jarkko
next prev parent reply other threads:[~2025-02-17 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 0:27 [PATCH v3 0/5] Add support for the TPM FF-A start method Stuart Yoder
2025-02-14 0:27 ` [PATCH v3 1/5] tpm_crb: implement driver compliant to CRB over FF-A Stuart Yoder
2025-02-14 7:44 ` Jarkko Sakkinen
2025-02-17 15:53 ` Stuart Yoder
2025-02-17 15:59 ` Jarkko Sakkinen [this message]
2025-02-14 0:27 ` [PATCH v3 2/5] tpm_crb: refactor check for idle support into TPM into inline function Stuart Yoder
2025-02-14 8:18 ` Jarkko Sakkinen
2025-02-17 15:54 ` Stuart Yoder
2025-02-14 0:27 ` [PATCH v3 3/5] ACPICA: add start method for Arm FF-A Stuart Yoder
2025-02-14 0:27 ` [PATCH v3 4/5] tpm_crb: add support for the Arm FF-A start method Stuart Yoder
2025-02-14 8:20 ` Jarkko Sakkinen
2025-02-17 15:56 ` Stuart Yoder
2025-02-14 0:27 ` [PATCH v3 5/5] Documentation: tpm: add documentation for the CRB FF-A interface Stuart Yoder
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=Z7Nc7Rs_bny6Bkyn@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 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).