[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0bc1734f-39c5-cf19-a77e-e0d08978b3d0@intel.com>
Date: Tue, 3 Aug 2021 08:40:06 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Lukas Bulwahn <lukas.bulwahn@...il.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
X86 ML <x86@...nel.org>, Randy Dunlap <rdunlap@...radead.org>,
"H . Peter Anvin" <hpa@...or.com>,
Darren Hart <dvhart@...radead.org>,
Andy Shevchenko <andy@...radead.org>,
Lubomir Rintel <lkundrak@...sk>, Pavel Machek <pavel@....cz>,
Lee Jones <lee.jones@...aro.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Linus Walleij <linus.walleij@...aro.org>,
platform-driver-x86@...r.kernel.org,
kernel-janitors <kernel-janitors@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kees Cook <keescook@...omium.org>
Subject: Re: [PATCH 0/9] Kconfig symbol clean-up on ./arch/x86/
On 8/3/21 8:12 AM, Lukas Bulwahn wrote:
>> It's a pretty safe guess that STRICT_IOMEM refers to CONFIG_STRICT_DEVMEM.
> Thanks, Dave.
>
> If the maintainers consider updates to comments making them consistent
> with the code as worth being picked, I will turn your analysis into a
> proper commit message and provide a patch to update that comment.
I'd happily ack a patch that does that. Might as well fix that kind of
stuff now before more time passes and it gets harder to track down.
Powered by blists - more mailing lists