[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d9d18954-8434-4c85-88b8-8e1d99cd6a4b@intel.com>
Date: Wed, 15 Feb 2023 09:11:56 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Jithu Joseph <jithu.joseph@...el.com>, hdegoede@...hat.com,
markgross@...nel.org
Cc: tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
gregkh@...uxfoundation.org, rostedt@...dmis.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 4/7] platform/x86/intel/ifs: Implement Array BIST test
On 2/15/23 08:58, Dave Hansen wrote:
> On 2/14/23 15:44, Jithu Joseph wrote:
> I'd probably do something like the attached patch. It gets rid of
> 'data' and uses sane types for the bitfield. It does away with separate
> variables and munging into/out of the msr[] array and just passes a
> single command struct to the work function. It doesn't have any
> uninitialized structure/bitfield fields.
Real patch attached now.
View attachment "ifs-fun.patch" of type "text/x-patch" (2818 bytes)
Powered by blists - more mailing lists