[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46ad3b08-b96b-6ef2-a5e4-fb0865865916@intel.com>
Date: Wed, 13 Feb 2019 08:40:22 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: "Bhardwaj, Rajneesh" <rajneesh.bhardwaj@...ux.intel.com>,
Borislav Petkov <bp@...en8.de>
Cc: platform-driver-x86@...r.kernel.org, dvhart@...radead.org,
andy@...radead.org, linux-kernel@...r.kernel.org, x86@...nel.org,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"David E. Box" <david.e.box@...el.com>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>
Subject: Re: [PATCH v2 06/10] x86/cpu: Add Icelake to Intel family
On 2/13/19 8:35 AM, Bhardwaj, Rajneesh wrote:
> I sure did, perhaps it wasn't clear in my response. I can remove
> coreboot link in next version but please clarify whether i should keep
> other link that i mentioned or just keep the commit without any link?
I think we're hearing loud and clear from the maintainers that they
prefer *public*, official documentation from Intel to back up our patches.
Barring that, they'd rather have no link than a link to some other
random project.
Powered by blists - more mailing lists