From: Borislav Petkov <bp@alien8.de>
To: Kyung Min Park <kyung.min.park@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org,
Rajneesh Bhardwaj <rajneesh.bhardwaj@linux.intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/cpu: Add Atom Tremont (Elkhart Lake)
Date: Tue, 13 Aug 2019 09:21:25 +0200 [thread overview]
Message-ID: <20190813072124.GA16770@zn.tnic> (raw)
In-Reply-To: <1565671419-5257-1-git-send-email-kyung.min.park@intel.com>
On Mon, Aug 12, 2019 at 09:43:38PM -0700, Kyung Min Park wrote:
> Add the Atom Tremont model number to the Intel family list.
>
> Signed-off-by: Kyung Min Park <kyung.min.park@intel.com>
> ---
> arch/x86/include/asm/intel-family.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/x86/include/asm/intel-family.h b/arch/x86/include/asm/intel-family.h
> index 0278aa6..02d675d 100644
> --- a/arch/x86/include/asm/intel-family.h
> +++ b/arch/x86/include/asm/intel-family.h
> @@ -79,6 +79,7 @@
> #define INTEL_FAM6_ATOM_GOLDMONT_PLUS 0x7A /* Gemini Lake */
>
> #define INTEL_FAM6_ATOM_TREMONT_X 0x86 /* Jacobsville */
> +#define INTEL_FAM6_ATOM_TREMONT 0x96 /* Elkhart Lake */
>
> /* Xeon Phi */
>
> --
Did you have a look at this thread before sending this patch?
https://lkml.kernel.org/r/20190808101045.19239-1-rajneesh.bhardwaj@linux.intel.com
Either way, please do a second patch summing up the naming scheme
explanations. And send this patch adding the model number together with
its first user patchset.
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
prev parent reply other threads:[~2019-08-13 7:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 4:43 [PATCH] x86/cpu: Add Atom Tremont (Elkhart Lake) Kyung Min Park
2019-08-13 7:21 ` Borislav Petkov [this message]
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=20190813072124.GA16770@zn.tnic \
--to=bp@alien8.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kan.liang@linux.intel.com \
--cc=kyung.min.park@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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