From: Mark Brown <broonie@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
Krishna Yarlagadda <kyarlagadda@nvidia.com>,
jsnitsel@redhat.com, robh+dt@kernel.org, peterhuewe@gmx.de,
jgg@ziepe.ca, krzysztof.kozlowski+dt@linaro.org,
linux-spi@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
jonathanh@nvidia.com, skomatineni@nvidia.com,
ldewangan@nvidia.com
Subject: Re: [Patch V10 2/3] tpm_tis-spi: Add hardware wait polling
Date: Mon, 24 Apr 2023 16:18:45 +0100 [thread overview]
Message-ID: <5fae29cd-d5f4-4616-be1c-1cd4d5b9a538@sirena.org.uk> (raw)
In-Reply-To: <ZEaWQD_QTs2usVl8@orome>
[-- Attachment #1: Type: text/plain, Size: 643 bytes --]
On Mon, Apr 24, 2023 at 04:46:24PM +0200, Thierry Reding wrote:
> Would it make sense for you to pick up patch 2/3 as well? As far as I
> can tell there's a build dependency on patch 1/3 because of the newly
> added SPI_TPM_HW_FLOW symbol.
I'll include it in my pull request for spi this time round so it should
end up in -rc1, my thinking was that I was happy with the SPI bits and
if it was in -rc1 then the TPM bits could be handled without cross tree
issues when the review was sorted (which it is now but wasn't at the
time). If the SPI side doesn't make -rc1 for some reason I can pick up
the TPM bit as well, and/or do a signed tag.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-04-24 15:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 9:13 [Patch V10 0/3] Tegra TPM driver with HW flow control Krishna Yarlagadda
2023-04-21 9:13 ` [Patch V10 1/3] spi: Add TPM HW flow flag Krishna Yarlagadda
2023-04-21 9:13 ` [Patch V10 2/3] tpm_tis-spi: Add hardware wait polling Krishna Yarlagadda
2023-04-23 15:08 ` Jarkko Sakkinen
2023-04-24 11:56 ` Mark Brown
2023-04-24 13:11 ` Jarkko Sakkinen
2023-04-24 14:46 ` Thierry Reding
2023-04-24 15:18 ` Mark Brown [this message]
2023-04-24 15:31 ` Thierry Reding
2023-05-10 15:10 ` Krishna Yarlagadda
2023-05-24 12:43 ` Krishna Yarlagadda
2023-06-01 8:29 ` Thierry Reding
2023-06-01 11:04 ` Mark Brown
2023-06-01 12:36 ` Thierry Reding
2023-06-01 12:40 ` Mark Brown
2023-06-09 14:19 ` Jarkko Sakkinen
2023-06-09 14:22 ` Mark Brown
2023-06-09 15:12 ` Jarkko Sakkinen
2023-04-21 9:13 ` [Patch V10 3/3] spi: tegra210-quad: Enable TPM " Krishna Yarlagadda
2023-04-21 9:39 ` Jon Hunter
2023-04-21 12:50 ` [Patch V10 0/3] Tegra TPM driver with HW flow control Jerry Snitselaar
2023-04-24 13:21 ` (subset) " Mark Brown
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=5fae29cd-d5f4-4616-be1c-1cd4d5b9a538@sirena.org.uk \
--to=broonie@kernel.org \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=jonathanh@nvidia.com \
--cc=jsnitsel@redhat.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kyarlagadda@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=robh+dt@kernel.org \
--cc=skomatineni@nvidia.com \
--cc=thierry.reding@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).