[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <238b55b0-7fe6-4923-ef8c-fb1cc1cd1c66@intel.com>
Date: Mon, 24 Oct 2022 15:57:21 -0700
From: Sohil Mehta <sohil.mehta@...el.com>
To: Jithu Joseph <jithu.joseph@...el.com>
CC: <tglx@...utronix.de>, <mingo@...hat.com>, <bp@...en8.de>,
<dave.hansen@...ux.intel.com>, <x86@...nel.org>, <hpa@...or.com>,
<gregkh@...uxfoundation.org>, <ashok.raj@...el.com>,
<tony.luck@...el.com>, <linux-kernel@...r.kernel.org>,
<platform-driver-x86@...r.kernel.org>, <patches@...ts.linux.dev>,
<ravi.v.shankar@...el.com>, <thiago.macieira@...el.com>,
<athenas.jimenez.gonzalez@...el.com>, <hdegoede@...hat.com>,
<markgross@...nel.org>
Subject: Re: [PATCH 03/14] platform/x86/intel/ifs: return a more appropriate
Error code
On 10/21/2022 1:34 PM, Jithu Joseph wrote:
> scan_chunks_sanity_check() was returning -ENOMEM if it encounters
> an error while copying IFS test image from memory to Secure Memory.
>
Same as before:
s/was returning/returns
> Return -EIO in this scenario, as it is more appropriate.
>
Do the first 3 patches need a 'Fixes' tag? Or is the idea here that the
feature isn't truly enabled so everything before removing the BROKEN tag
will be considered together?
Powered by blists - more mailing lists