From: Jarkko Sakkinen <jarkko@kernel.org>
To: MicroFish <f13208471983@163.com>
Cc: jgg@ziepe.ca, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org, peterhuewe@gmx.de,
stable@vger.kernel.org
Subject: Re: [PATCH] tpm: crb: handle ACPI NVS memory region overlap
Date: Tue, 1 Sep 2026 15:57:38 +0300 [thread overview]
Message-ID: <apbLwhETZei6Lhi9@kernel.org> (raw)
In-Reply-To: <20260828111141.1515-1-f13208471983@163.com>
On Fri, Aug 28, 2026 at 07:11:41PM +0800, MicroFish wrote:
> On Fri, Aug 28, 2026 at 05:04:54AM +0300, Jarkko Sakkinen wrote:
>
> > Cannot and will not move forward given undefined and open set of gear.
> >
> > There was also a corrupted email address in the CC list (microfish at
> > kernel dot org).
>
> Thanks for the review.
>
> The affected hardware I have confirmed is the Lenovo ThinkPad E475
> with an AMD APU.
>
> This is the platform on which I reproduced the ACPI NVS and TPM CRB
> MMIO region overlap described in the patch.
>
> The incorrect CC address was my mistake. The correct address is
> [f13208471983@163.com](mailto:f13208471983@163.com).
>
> Best regards,
> microfish
>
Please only claim what you have quantitative proof for.
Also this is faulty:
Signed-off-by: microfish <microfish@kernel.org>
I'm not happy with the code change but I'll try to propose something
once I have the bandwidth. Need to think about it a bit.
BR, Jarkko
next prev parent reply other threads:[~2026-09-01 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 3:55 microfish
2026-08-28 2:04 ` Jarkko Sakkinen
2026-08-28 11:11 ` MicroFish
2026-09-01 12:57 ` Jarkko Sakkinen [this message]
2026-09-01 14:35 ` 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=apbLwhETZei6Lhi9@kernel.org \
--to=jarkko@kernel.org \
--cc=f13208471983@163.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=stable@vger.kernel.org \
/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®