From: Borislav Petkov <bp@alien8.de>
To: Dave Hansen <dave.hansen@intel.com>,
"Liang, Kan" <kan.liang@linux.intel.com>
Cc: "Bhardwaj, Rajneesh" <rajneesh.bhardwaj@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
x86@kernel.org, bp@suse.de,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>, Len Brown <lenb@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] x86/cpu: Add Elkhart Lake to Intel family
Date: Thu, 8 Aug 2019 18:38:49 +0200 [thread overview]
Message-ID: <20190808163849.GL20745@zn.tnic> (raw)
In-Reply-To: <7ba45ead-186a-8802-2da6-6fa9fa00b36a@intel.com>
On Thu, Aug 08, 2019 at 09:30:49AM -0700, Dave Hansen wrote:
> Could someone also add some "how to add an entry to this file" in the
> top of that file? We seem to have the same, tortuous conversations
> about one-line patches each time.
There is some doc at the top:
/*
* "Big Core" Processors (Branded as Core, Xeon, etc...)
*
* The "_X" parts are generally the EP and EX Xeons, or the
* "Extreme" ones, like Broadwell-E, or Atom microserver.
but that nomenclature doesn't seem to pan out here.
We could call it
...ATOM_TREMONT_C
or so to mean client, similar to the _X thing.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-08-08 16:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 10:10 [PATCH] x86/cpu: Add Elkhart Lake to Intel family Rajneesh Bhardwaj
2019-08-08 10:42 ` Peter Zijlstra
2019-08-08 12:28 ` Bhardwaj, Rajneesh
2019-08-08 12:47 ` Peter Zijlstra
2019-08-08 13:19 ` Liang, Kan
2019-08-08 13:56 ` Dave Hansen
2019-08-08 15:14 ` Bhardwaj, Rajneesh
2019-08-08 15:24 ` Borislav Petkov
2019-08-08 14:14 ` Peter Zijlstra
2019-08-08 15:10 ` Bhardwaj, Rajneesh
2019-08-08 15:16 ` Borislav Petkov
2019-08-08 15:23 ` Peter Zijlstra
2019-08-08 15:28 ` Borislav Petkov
2019-08-08 15:31 ` Peter Zijlstra
2019-08-08 15:50 ` Bhardwaj, Rajneesh
2019-08-08 16:27 ` Liang, Kan
2019-08-08 16:30 ` Dave Hansen
2019-08-08 16:38 ` Borislav Petkov [this message]
2019-08-08 16:54 ` Dave Hansen
2019-08-08 17:30 ` Borislav Petkov
2019-08-08 19:24 ` Dave Hansen
2019-08-08 19:30 ` Borislav Petkov
2019-08-08 17:54 ` Peter Zijlstra
2019-08-08 17:38 ` Peter Zijlstra
2019-08-08 17:37 ` Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190808163849.GL20745@zn.tnic \
--to=bp@alien8.de \
--cc=bp@suse.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kan.liang@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=qiuxu.zhuo@intel.com \
--cc=rajneesh.bhardwaj@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox