From: Dave Hansen <dave.hansen@intel.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
linux-kernel@vger.kernel.org, linux-coco@lists.linux.dev,
kvm@vger.kernel.org
Cc: x86@kernel.org, Chao Gao <chao.gao@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Kai Huang <kai.huang@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Kiryl Shutsemau <kas@kernel.org>,
Rick Edgecombe <rick.p.edgecombe@intel.com>
Subject: Re: [PATCH v2 1/2] x86/virt/tdx: Retrieve TDX module version
Date: Mon, 12 Jan 2026 06:56:58 -0800 [thread overview]
Message-ID: <f0cc6afe-0f58-4314-9a77-34c5b005b677@intel.com> (raw)
In-Reply-To: <93ab41bc-91bf-405a-84c4-6355a556596d@intel.com>
On 1/11/26 18:25, Xiaoyao Li wrote:
> ... I know it's because minor_version has the least field ID among the
> three. But the order of the field IDs doesn't stand for the order of the
> reading. Reading the middle part y of x.y.z as first step looks a bit odd.
I wouldn't sweat it either way. Reading 4, 3, 5 would also look odd. I'm
fine with it as-is in the patch.
next prev parent reply other threads:[~2026-01-12 14:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 19:14 [PATCH v2 0/2] x86/virt/tdx: Print TDX module version to dmesg Vishal Verma
2026-01-09 19:14 ` [PATCH v2 1/2] x86/virt/tdx: Retrieve TDX module version Vishal Verma
2026-01-12 2:25 ` Xiaoyao Li
2026-01-12 14:56 ` Dave Hansen [this message]
2026-01-13 2:56 ` Xu Yilun
2026-01-13 3:58 ` Xiaoyao Li
2026-01-12 8:30 ` Binbin Wu
2026-01-19 8:12 ` Tony Lindgren
2026-01-09 19:14 ` [PATCH v2 2/2] x86/virt/tdx: Print TDX module version during init Vishal Verma
2026-01-09 20:00 ` Edgecombe, Rick P
2026-01-12 2:31 ` Xiaoyao Li
2026-01-12 8:32 ` Binbin Wu
2026-01-12 11:23 ` Kiryl Shutsemau
2026-01-19 8:12 ` Tony Lindgren
2026-01-11 22:15 ` [PATCH v2 0/2] x86/virt/tdx: Print TDX module version to dmesg Huang, Kai
2026-02-05 19:05 ` Verma, Vishal L
2026-02-06 11:39 ` Kiryl Shutsemau
2026-02-06 15:10 ` Dave Hansen
2026-02-06 18:35 ` Edgecombe, Rick P
2026-02-09 10:46 ` Kiryl Shutsemau
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=f0cc6afe-0f58-4314-9a77-34c5b005b677@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kai.huang@intel.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=tglx@linutronix.de \
--cc=vishal.l.verma@intel.com \
--cc=x86@kernel.org \
--cc=xiaoyao.li@intel.com \
/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