[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a84cf78f-dd30-4847-a503-e10f547862ad@intel.com>
Date: Mon, 19 Jan 2026 08:24:05 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Chao Gao <chao.gao@...el.com>, "H. Peter Anvin" <hpa@...or.com>
Cc: Xu Yilun <yilun.xu@...ux.intel.com>, linux-coco@...ts.linux.dev,
linux-kernel@...r.kernel.org, x86@...nel.org, reinette.chatre@...el.com,
ira.weiny@...el.com, kai.huang@...el.com, dan.j.williams@...el.com,
sagis@...gle.com, vannapurve@...gle.com, paulmck@...nel.org,
nik.borisov@...e.com, Farrah Chen <farrah.chen@...el.com>,
"Kirill A. Shutemov" <kas@...nel.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH v2 16/21] x86/virt/seamldr: Handle TDX Module update
failures
On 1/18/26 21:34, Chao Gao wrote:
> On Sun, Jan 18, 2026 at 08:55:22PM -0800, H. Peter Anvin wrote:
>> On January 14, 2026 10:24:22 PM PST, Xu Yilun <yilun.xu@...ux.intel.com> wrote:
>>> On Tue, Sep 30, 2025 at 07:53:00PM -0700, Chao Gao wrote:
>>>> Failures encountered after a successful module shutdown are unrecoverable,
>>>> e.g., there is no way to restore the old TDX Module.
>>> "e.g." is obscure. To me, the following sentence is explaining the
>>> reason why the failure is not recoverable. Maybe "i.e." or "because"?
>> "e.g." (for example) means the following list is non-exhaustive.
> Yes, 'i.e.' or 'because' would be more appropriate since the next sentence
> explains 'unrecoverable'.
FWIW, I very much prefer plain words. "i.e." and "e.g." are really only
useful if you and all your readers know how they work.
I don't feel the need to be draconian about it, but I frankly *wish*
folks would just remove them from their written vocabulary.
Powered by blists - more mailing lists