[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F7D4E216D@ORSMSX110.amr.corp.intel.com>
Date: Fri, 1 Feb 2019 19:18:35 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Johannes Weiner <hannes@...xchg.org>, Borislav Petkov <bp@...e.de>
CC: Babu Moger <babu.moger@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Yu, Fenghua" <fenghua.yu@...el.com>,
"Chatre, Reinette" <reinette.chatre@...el.com>
Subject: RE: [PATCH] x86: avoid confusion over the new RESCTRL config prompt
>> What about
>>
>> s/X86_RESCTRL/X86_CPU_RESCTRL/g
>
> Good idea.
>
> Tony, Babu, that look okay to you guys as well?
For now. But very soon we will also have ARM_CPU_RESCTRL, and some of
this code will become generic. Will we need an arch-independent name for the
bits of code shared by arm and x86?
-Tony
Powered by blists - more mailing lists