From: Thorsten Blum <thorsten.blum@linux.dev>
To: Jarkko Sakkinen <jarkko@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>
Cc: x86@kernel.org, linux-sgx@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] x86/sgx: Remove unused definitions and reuse launch token size
Date: Mon, 31 Aug 2026 10:07:02 +0200 [thread overview]
Message-ID: <apU2JrX7Dl5VrvxV@linux.dev> (raw)
In-Reply-To: <20260729125624.514697-5-thorsten.blum@linux.dev>
On Wed, Jul 29, 2026 at 02:56:25PM +0200, Thorsten Blum wrote:
> Remove SGX definitions that have never had in-tree users and reuse
> SGX_LAUNCH_TOKEN_SIZE when validating the launch token in
> __sgx_virt_einit().
>
> Changes in v2:
> - Adjust commit message 3/3 as suggested by Kai
> - v1: https://lore.kernel.org/r/20260711100053.739588-5-thorsten.blum@linux.dev/
>
> Thorsten Blum (3):
> x86/sgx: Remove unused TCS definitions
> x86/sgx: Remove unused size and count definitions
> x86/sgx: Use SGX_LAUNCH_TOKEN_SIZE in __sgx_virt_einit()
>
> arch/x86/include/asm/sgx.h | 59 ----------------------------------
> arch/x86/kernel/cpu/sgx/virt.c | 3 +-
> 2 files changed, 1 insertion(+), 61 deletions(-)
>
>
> base-commit: 2d3090a8aeb596a26935db0955d46c9a5db5c6ce
Gentle ping - all 3 patches have had Reviewed-by: and/or Acked-by: tags
since mid-July. Is there anything missing or can these be applied?
Thanks,
Thorsten
prev parent reply other threads:[~2026-08-31 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 12:56 [PATCH v2 0/3] x86/sgx: Remove unused definitions and reuse launch token size Thorsten Blum
2026-07-29 12:56 ` [PATCH v2 1/3] x86/sgx: Remove unused TCS definitions Thorsten Blum
2026-07-29 12:56 ` [PATCH v2 2/3] x86/sgx: Remove unused size and count definitions Thorsten Blum
2026-07-29 12:56 ` [PATCH v2 3/3] x86/sgx: Use SGX_LAUNCH_TOKEN_SIZE in __sgx_virt_einit() Thorsten Blum
2026-08-31 8:07 ` Thorsten Blum [this message]
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=apU2JrX7Dl5VrvxV@linux.dev \
--to=thorsten.blum@linux.dev \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--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.