[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DM8PR11MB5750B9D8DA723CF88500333EE722A@DM8PR11MB5750.namprd11.prod.outlook.com>
Date: Tue, 5 Aug 2025 10:11:21 +0000
From: "Reshetova, Elena" <elena.reshetova@...el.com>
To: "Hansen, Dave" <dave.hansen@...el.com>
CC: "jarkko@...nel.org" <jarkko@...nel.org>, "seanjc@...gle.com"
<seanjc@...gle.com>, "Huang, Kai" <kai.huang@...el.com>, "mingo@...nel.org"
<mingo@...nel.org>, "linux-sgx@...r.kernel.org" <linux-sgx@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>, "Mallick, Asit K"
<asit.k.mallick@...el.com>, "Scarlata, Vincent R"
<vincent.r.scarlata@...el.com>, "Cai, Chong" <chongc@...gle.com>, "Aktas,
Erdem" <erdemaktas@...gle.com>, "Annapurve, Vishal" <vannapurve@...gle.com>,
"Bondarevska, Nataliia" <bondarn@...gle.com>, "Raynor, Scott"
<scott.raynor@...el.com>
Subject: RE: [PATCH v10 4/6] x86/sgx: Define error codes for use by
ENCLS[EUPDATESVN]
> -----Original Message-----
> From: Hansen, Dave <dave.hansen@...el.com>
> Sent: Monday, August 4, 2025 5:20 PM
> To: Reshetova, Elena <elena.reshetova@...el.com>
> Cc: jarkko@...nel.org; seanjc@...gle.com; Huang, Kai
> <kai.huang@...el.com>; mingo@...nel.org; linux-sgx@...r.kernel.org; linux-
> kernel@...r.kernel.org; x86@...nel.org; Mallick, Asit K
> <asit.k.mallick@...el.com>; Scarlata, Vincent R <vincent.r.scarlata@...el.com>;
> Cai, Chong <chongc@...gle.com>; Aktas, Erdem <erdemaktas@...gle.com>;
> Annapurve, Vishal <vannapurve@...gle.com>; Bondarevska, Nataliia
> <bondarn@...gle.com>; Raynor, Scott <scott.raynor@...el.com>
> Subject: Re: [PATCH v10 4/6] x86/sgx: Define error codes for use by
> ENCLS[EUPDATESVN]
>
> On 8/4/25 00:21, Reshetova, Elena wrote:
> ...
> >>> + EUPDATESVN = 0x18,
> >>> };
> >>
> >> This update is not consistent with the changelog nor the patch subject.
> >
> > I can remove the alignment fix.
>
> It's not the alignment.
>
> It's the definition of EUPDATESVN that goes completely unmentioned.
Yes, good catch, this should be moved to the next patch indeed.
>
> ...
> >> Ideally, we find a way to relay this in a very succinct way.
> >
> > Could you please elaborate what you mean by this?
> > Changing the description? The name or?
>
> Relaying it in the comment next to the definition would be best.
Sure, will try to extend the current description to convey it better.
Best Regards,
Elena.
Powered by blists - more mailing lists