[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1836a770-86ce-fc34-f7fd-6d1692fa184a@linux.intel.com>
Date: Wed, 13 Feb 2019 22:43:30 +0530
From: "Bhardwaj, Rajneesh" <rajneesh.bhardwaj@...ux.intel.com>
To: Dave Hansen <dave.hansen@...el.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 13-Feb-19 10:10 PM, Dave Hansen wrote:
> 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.
Thank you Dave for the clarification.
Hi Borislav, I realize that the link i mentioned is not public.
Apologies for creating confusion around that and for the previous top
posting. I will drop references to the coreboot link too in the next
version.
>
Powered by blists - more mailing lists