From: Jarkko Sakkinen <jarkko@kernel.org>
To: Axel Rasmussen <axelrasmussen@google.com>
Cc: Jacqueline Wong <jacqwong@google.com>,
linux-integrity@vger.kernel.org, peterhuewe@gmx.de, jgg@ziepe.ca,
jhand@google.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] tpm_tis: fix retry exhaustion and add logging
Date: Thu, 23 Apr 2026 13:21:23 +0300 [thread overview]
Message-ID: <aenyoxT8ITZ6NBDk@kernel.org> (raw)
In-Reply-To: <CAJHvVcgnsh-PeSsemRd6crAUP85sqzMSZ1mcS08ATJr7cAvAaA@mail.gmail.com>
On Wed, Apr 22, 2026 at 04:00:17PM -0700, Axel Rasmussen wrote:
> On Wed, Apr 15, 2026 at 9:00 AM Jacqueline Wong <jacqwong@google.com> wrote:
> >
> > The Fix:
> > - Patch 1: Adds error logs to identify the specific hardware status mismatch.
> > - Patch 2: Stops execution immediately when retries are exhausted.
> >
> > v3 changes:
> > - Improved code alignment to pass checkpatch --strict.
>
> Thanks for sending the v3 Jacqueline!
> I suspect this may have slipped under folks' radar by not CC'ing +linux-kernel@.
Please check that I carry the correct version of patches:
https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/log/?h=for-next-tpm
This is related to:
1. https://lore.kernel.org/linux-integrity/aeVSbVIFaCDRXf7C@kernel.org/
2. https://lore.kernel.org/linux-integrity/CAHk-=wiPWCUHsNvzKep7z4VGaL-Brx6Zmh7Efn28WWTPbwn5dA@mail.gmail.com/
3. https://lore.kernel.org/all/aee_mCW8p2J6IbIO@kernel.org/
I will try to send PRs after my split next branches are sync to -next.
BR, Jarkko
next prev parent reply other threads:[~2026-04-23 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 16:00 [PATCH v3 0/2] tpm_tis: fix retry exhaustion and add logging Jacqueline Wong
2026-04-15 16:00 ` [PATCH v3 1/2] tpm: tpm_tis: add error logging for data transfer Jacqueline Wong
2026-04-15 16:00 ` [PATCH v3 2/2] tpm: tpm_tis: stop transmit if retries are exhausted Jacqueline Wong
2026-04-22 23:00 ` [PATCH v3 0/2] tpm_tis: fix retry exhaustion and add logging Axel Rasmussen
2026-04-23 10:21 ` Jarkko Sakkinen [this message]
[not found] ` <CAK8FdkqPzOiZZHsZPbMQg0s_=+rU6ENtBx-6YtuekyiqG8cvPw@mail.gmail.com>
2026-04-23 16:43 ` 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=aenyoxT8ITZ6NBDk@kernel.org \
--to=jarkko@kernel.org \
--cc=axelrasmussen@google.com \
--cc=jacqwong@google.com \
--cc=jgg@ziepe.ca \
--cc=jhand@google.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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