[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48b6d063-8528-2208-5117-5c9c095886e5@intel.com>
Date: Fri, 28 Jul 2023 15:36:42 -0700
From: Sohil Mehta <sohil.mehta@...el.com>
To: Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>
CC: <x86@...nel.org>, Tom Lendacky <thomas.lendacky@....com>,
Andrew Cooper <andrew.cooper3@...rix.com>,
Arjan van de Ven <arjan@...ux.intel.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
Dick Kennedy <dick.kennedy@...adcom.com>,
James Smart <james.smart@...adcom.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
<linux-scsi@...r.kernel.org>, Guenter Roeck <linux@...ck-us.net>,
<linux-hwmon@...r.kernel.org>, "Jean Delvare" <jdelvare@...e.com>,
Huang Rui <ray.huang@....com>, Juergen Gross <jgross@...e.com>,
Steve Wahl <steve.wahl@....com>,
Mike Travis <mike.travis@....com>,
Dimitri Sivanich <dimitri.sivanich@....com>,
"Russ Anderson" <russ.anderson@....com>
Subject: Re: [patch v2 11/38] x86/apic: Use BAD_APICID consistently;
There is an extra semicolon at the end of the patch subject.
On 7/28/2023 5:12 AM, Thomas Gleixner wrote:
> APIC ID checks compare with BAD_APICID all over the place, but some
> initializers and some code which fiddles with global data structure use
> -1[U] instead. That simply cannot work at all.
>
> Fix it up and use BAD_APICID consistenly all over the place.
>
s/consistenly/consistently
-Sohil
Powered by blists - more mailing lists