public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: Andi Kleen <ak@linux.intel.com>,
	kan.liang@linux.intel.com, mingo@redhat.com, len.brown@intel.com,
	linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] x86/cpu: Rename Denverton and Gemini Lake
Date: Thu, 27 Sep 2018 07:53:24 -0700	[thread overview]
Message-ID: <8958caf1-08b8-60f9-6ef1-8abf99cbd5de@linux.intel.com> (raw)
In-Reply-To: <20180927142519.GB3439@hirez.programming.kicks-ass.net>

On 09/27/2018 07:25 AM, Peter Zijlstra wrote:
> #define INTEL_FAM6_ATOM_GOLDMONT	0x5C /* Apollo Lake */
> #define INTEL_FAM6_ATOM_GOLDMONT_X	0x5F /* Denvertor */
> #define INTEL_FAM6_ATOM_GOLDMONT_PLUS	0x7A /* Gemini Lake */

s/Denvertor/Denverton/

But, yeah, that list looks consistent and sane.

  parent reply	other threads:[~2018-09-27 14:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-07 17:17 [PATCH] x86/cpu: Rename Denverton and Gemini Lake kan.liang
2018-08-07 17:34 ` Peter Zijlstra
2018-08-07 17:35 ` Dave Hansen
2018-08-07 17:48   ` Peter Zijlstra
2018-08-07 18:29     ` Dave Hansen
2018-08-07 18:37     ` Andi Kleen
2018-08-07 19:59       ` Peter Zijlstra
2018-08-07 21:10       ` Thomas Gleixner
2018-08-07 22:17         ` Andi Kleen
2018-08-08  5:14           ` Thomas Gleixner
2018-08-08 14:07             ` Arnd Bergmann
2018-09-27 14:25             ` Peter Zijlstra
2018-09-27 14:49               ` Thomas Gleixner
2018-09-27 14:57                 ` Peter Zijlstra
2018-09-27 15:00                   ` Thomas Gleixner
2018-09-27 14:53               ` Dave Hansen [this message]
2018-09-28 16:07               ` Alan Cox
2018-09-28 19:18                 ` Peter Zijlstra
2018-08-07 18:35 ` Andi Kleen

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=8958caf1-08b8-60f9-6ef1-8abf99cbd5de@linux.intel.com \
    --to=dave.hansen@linux.intel.com \
    --cc=ak@linux.intel.com \
    --cc=kan.liang@linux.intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --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