From: "Huang, Kai" <kai.huang@intel.com>
To: "jarkko@kernel.org" <jarkko@kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"bp@alien8.de" <bp@alien8.de>,
"thorsten.blum@linux.dev" <thorsten.blum@linux.dev>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"x86@kernel.org" <x86@kernel.org>,
"tglx@kernel.org" <tglx@kernel.org>
Cc: "linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] x86/sgx: Remove unused size and count definitions
Date: Tue, 14 Jul 2026 00:24:38 +0000 [thread overview]
Message-ID: <4e6d8f164ea0092043b9d57633ec619d37d94a93.camel@intel.com> (raw)
In-Reply-To: <20260711100053.739588-7-thorsten.blum@linux.dev>
On Sat, 2026-07-11 at 12:00 +0200, Thorsten Blum wrote:
> The definitions were added with commit 70d3b8ddcd20 ("x86/sgx: Add SGX
> architectural data structures"), but have never been used. The SIGSTRUCT
> reserved field sizes are also redundant because the structure uses
> literal sizes instead. Remove them.
>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
Acked-by: Kai Huang <kai.huang@intel.com>
next prev parent reply other threads:[~2026-07-14 0:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 10:00 [PATCH 0/3] x86/sgx: Remove unused definitions and reuse launch token size Thorsten Blum
2026-07-11 10:00 ` [PATCH 1/3] x86/sgx: Remove unused TCS definitions Thorsten Blum
2026-07-11 18:22 ` Jarkko Sakkinen
2026-07-14 0:23 ` Huang, Kai
2026-07-11 10:00 ` [PATCH 2/3] x86/sgx: Remove unused size and count definitions Thorsten Blum
2026-07-11 18:22 ` Jarkko Sakkinen
2026-07-14 0:24 ` Huang, Kai [this message]
2026-07-11 10:00 ` [PATCH 3/3] x86/sgx: Use SGX_LAUNCH_TOKEN_SIZE in __sgx_virt_einit() Thorsten Blum
2026-07-11 18:23 ` Jarkko Sakkinen
2026-07-14 0:21 ` Huang, Kai
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=4e6d8f164ea0092043b9d57633ec619d37d94a93.camel@intel.com \
--to=kai.huang@intel.com \
--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=thorsten.blum@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox