[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7d4b5f20-68c2-5464-aeb9-a3afaf52b827@intel.com>
Date: Thu, 10 Nov 2022 13:58:39 -0800
From: "Joseph, Jithu" <jithu.joseph@...el.com>
To: Hans de Goede <hdegoede@...hat.com>, Borislav Petkov <bp@...en8.de>
CC: <markgross@...nel.org>, <tglx@...utronix.de>, <mingo@...hat.com>,
<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>, <sohil.mehta@...el.com>
Subject: Re: [PATCH v2 00/14] IFS multi test image support and misc changes
On 11/10/2022 1:37 PM, Hans de Goede wrote:
> Hi Boris,
>
> On 11/10/22 10:59, Borislav Petkov wrote:
>> On Mon, Nov 07, 2022 at 02:53:09PM -0800, Jithu Joseph wrote:
>>> Changes in v2
>>> - Rebased ontop of v6.1-rc4
>>> Boris
>>> - Moved exported functions (microcode_sanity_check(),
>>> find_matching_signature ) from microcode/intel.c to cpu/intel.c
>>> (patch4,6)
>>> - Removed microcode metadata specific code changes to
>>> microcode_sanity_check() (patch6)
>>> - Moved find_meta_data() from common to IFS driver (Patch 8)
>>
>> What's the upstreaming plan here - I'm assuming I should take the
>> microcode patches through the tip tree?
>>
>> Or should I take the whole thing through tip so that there's no
>> confusion and having to sync and share branches between trees?
>
> I have just reviewed all the platform/x86/intel/ifs changes
> and they all look good to me.
>
Hans, Thanks for reviewing.
Boris, I have fixes from Sohil's comments (mainly for patch 06/14). Let me know
if you have any other issues that need touching up in x86 parts (04 - 07).
I will post a cleaned-up series next week.
Jithu
Powered by blists - more mailing lists