From: Jarkko Sakkinen <jarkko@kernel.org>
To: ross.philipson@oracle.com, linux-kernel@vger.kernel.org,
x86@kernel.org, linux-integrity@vger.kernel.org,
linux-doc@vger.kernel.org, linux-crypto@vger.kernel.org,
kexec@lists.infradead.org, linux-efi@vger.kernel.org,
iommu@lists.linux-foundation.org
Cc: dpsmith@apertussolutions.com, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, hpa@zytor.com,
dave.hansen@linux.intel.com, ardb@kernel.org,
mjg59@srcf.ucam.org, James.Bottomley@hansenpartnership.com,
peterhuewe@gmx.de, jgg@ziepe.ca, luto@amacapital.net,
nivedita@alum.mit.edu, herbert@gondor.apana.org.au,
davem@davemloft.net, corbet@lwn.net, ebiederm@xmission.com,
dwmw2@infradead.org, baolu.lu@linux.intel.com,
kanth.ghatraju@oracle.com, andrew.cooper3@citrix.com,
trenchboot-devel@googlegroups.com
Subject: Re: [PATCH v12 00/19] x86: Trenchboot secure dynamic launch Linux kernel support
Date: Tue, 18 Feb 2025 20:31:35 +0200 [thread overview]
Message-ID: <eaa0d608fb78d06caca26edc9a830cf1a02f9fb8.camel@kernel.org> (raw)
In-Reply-To: <060ffc99-59e8-4b71-9e7d-daeb807332c3@oracle.com>
On Tue, 2025-02-18 at 10:21 -0800, ross.philipson@oracle.com wrote:
> Hello folks,
>
> We posted the v12 version of our patch set in December of 2024 and we
> have not heard anything on it from the community. We believe we have
> reasonably addressed the issues as has been discussed on list. I
> realize
> there has been a lot going on with releases etc but I just wanted to
> send a bump that these patches are out there if anyone has time.
I don't know what happened but to be totally honest with you I missed
that version. Maybe it was holiday rush but yeah still I did not skip
it for that reason per se, just that it could very well explain the
silence (people tend to fast-forward more at the time, and then
mistakes easily happen).
I'm right now on holiday up until end of this month, and this will
require enough time that I unfortunately have to postpone the review
up until the first full week of the next Month, in order to do this
properly.
Still, apologies for ignoring this!
> Thank you,
> Ross Philipson
BR, Jarkko
next prev parent reply other threads:[~2025-02-18 18:40 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 19:41 [PATCH v12 00/19] x86: Trenchboot secure dynamic launch Linux kernel support Ross Philipson
2024-12-19 19:41 ` [PATCH v12 01/19] Documentation/x86: Secure Launch kernel documentation Ross Philipson
2025-03-07 5:10 ` Jarkko Sakkinen
2025-03-07 5:15 ` Jarkko Sakkinen
2024-12-19 19:41 ` [PATCH v12 02/19] x86: Secure Launch Kconfig Ross Philipson
2024-12-19 19:42 ` [PATCH v12 03/19] x86: Secure Launch Resource Table header file Ross Philipson
2025-03-07 5:32 ` Jarkko Sakkinen
2025-03-07 19:22 ` ross.philipson
2025-03-07 19:30 ` Jarkko Sakkinen
2025-03-07 19:44 ` ross.philipson
2024-12-19 19:42 ` [PATCH v12 04/19] x86: Secure Launch main " Ross Philipson
2025-03-07 5:34 ` Jarkko Sakkinen
2025-03-07 19:25 ` ross.philipson
2025-03-07 19:37 ` Jarkko Sakkinen
2025-03-07 19:46 ` ross.philipson
2024-12-19 19:42 ` [PATCH v12 05/19] x86: Add early SHA-1 support for Secure Launch early measurements Ross Philipson
2025-03-07 5:35 ` Jarkko Sakkinen
2024-12-19 19:42 ` [PATCH v12 06/19] x86: Add early SHA-256 " Ross Philipson
2025-03-07 5:36 ` Jarkko Sakkinen
2024-12-19 19:42 ` [PATCH v12 07/19] x86/msr: Add variable MTRR base/mask and x2apic ID registers Ross Philipson
2025-03-07 5:55 ` Jarkko Sakkinen
2025-03-07 19:29 ` ross.philipson
2024-12-19 19:42 ` [PATCH v12 08/19] x86/boot: Place TXT MLE header in the kernel_info section Ross Philipson
2025-03-07 6:51 ` Jarkko Sakkinen
2025-03-07 19:33 ` ross.philipson
2024-12-19 19:42 ` [PATCH v12 09/19] x86: Secure Launch kernel early boot stub Ross Philipson
2025-03-07 7:00 ` Jarkko Sakkinen
2025-03-07 19:42 ` ross.philipson
2024-12-19 19:42 ` [PATCH v12 10/19] x86: Secure Launch kernel late " Ross Philipson
2025-03-07 7:02 ` Jarkko Sakkinen
2025-03-07 19:43 ` ross.philipson
2024-12-19 19:42 ` [PATCH v12 11/19] x86: Secure Launch SMP bringup support Ross Philipson
2024-12-19 19:42 ` [PATCH v12 12/19] kexec: Secure Launch kexec SEXIT support Ross Philipson
2024-12-19 19:42 ` [PATCH v12 13/19] x86/reboot: Secure Launch SEXIT support on reboot paths Ross Philipson
2024-12-19 19:42 ` [PATCH v12 14/19] tpm, tpm_tis: Close all localities Ross Philipson
2025-03-07 7:05 ` Jarkko Sakkinen
2024-12-19 19:42 ` [PATCH v12 15/19] tpm, tpm_tis: Address positive localities in tpm_tis_request_locality() Ross Philipson
2025-03-07 7:07 ` Jarkko Sakkinen
2025-03-07 19:35 ` ross.philipson
2024-12-19 19:42 ` [PATCH v12 16/19] tpm, tpm_tis: Allow locality to be set to a different value Ross Philipson
2025-03-07 7:07 ` Jarkko Sakkinen
2024-12-19 19:42 ` [PATCH v12 17/19] tpm, sysfs: Show locality used by kernel Ross Philipson
2025-03-07 7:09 ` Jarkko Sakkinen
2025-03-07 19:39 ` ross.philipson
2024-12-19 19:42 ` [PATCH v12 18/19] x86: Secure Launch late initcall platform module Ross Philipson
2024-12-19 19:42 ` [PATCH v12 19/19] x86/efi: EFI stub DRTM launch support for Secure Launch Ross Philipson
2025-02-18 18:21 ` [PATCH v12 00/19] x86: Trenchboot secure dynamic launch Linux kernel support ross.philipson
2025-02-18 18:31 ` Jarkko Sakkinen [this message]
2025-02-18 19:39 ` ross.philipson
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=eaa0d608fb78d06caca26edc9a830cf1a02f9fb8.camel@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=andrew.cooper3@citrix.com \
--cc=ardb@kernel.org \
--cc=baolu.lu@linux.intel.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dpsmith@apertussolutions.com \
--cc=dwmw2@infradead.org \
--cc=ebiederm@xmission.com \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jgg@ziepe.ca \
--cc=kanth.ghatraju@oracle.com \
--cc=kexec@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=mjg59@srcf.ucam.org \
--cc=nivedita@alum.mit.edu \
--cc=peterhuewe@gmx.de \
--cc=ross.philipson@oracle.com \
--cc=tglx@linutronix.de \
--cc=trenchboot-devel@googlegroups.com \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.