[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171031182540.rcmzqjvmzbarjfpj@pd.tnic>
Date: Tue, 31 Oct 2017 19:25:40 +0100
From: Borislav Petkov <bp@...en8.de>
To: "Yu, Fenghua" <fenghua.yu@...el.com>
Cc: "Kammela, Gayatri" <gayatri.kammela@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"hpa@...ux.intel.com" <hpa@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
"Kleen, Andi" <andi.kleen@...el.com>,
"Shankar, Ravi V" <ravi.v.shankar@...el.com>,
"Neri, Ricardo" <ricardo.neri@...el.com>,
"Zhong, Yang" <yang.zhong@...el.com>
Subject: Re: [PATCH v2] x86/cpufeatures: Enable new SSE/AVX/AVX512 cpu
features
On Tue, Oct 31, 2017 at 06:02:53PM +0000, Yu, Fenghua wrote:
> As you said, the legacy code doesn't follow spec naming strictly
> and the spec doesn't have uniform naming convention either. We are
> contacting spec author to see if we can follow the same naming
> convention in the future specs.
Whatever you do, you should change it before it hits mainline because
then it becomes user-space visible. So you can fix the kernel format
first and then concentrate on changing the spec.
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists