mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tanwar, Rahul" <rahul.tanwar@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>, Tony Luck <tony.luck@intel.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	x86@kernel.org, andriy.shevchenko@intel.com,
	alan@linux.intel.com, ricardo.neri-calderon@linux.intel.com,
	rafael.j.wysocki@intel.com, linux-kernel@vger.kernel.org,
	qi-ming.wu@intel.com, cheol.yong.kim@intel.com,
	rahul.tanwar@intel.com
Subject: Re: [PATCH 2/3] x86: cpu: Add new Intel Atom CPU type
Date: Fri, 16 Aug 2019 11:22:16 +0800	[thread overview]
Message-ID: <68ad47a7-ac6f-0a1b-0892-850bb95c002b@linux.intel.com> (raw)
In-Reply-To: <20190815122222.GE15313@zn.tnic>


Hi Boris,

Well noted, will have Tony in loop from now on. Thanks.

Regards,

Rahul

On 15/8/2019 8:22 PM, Borislav Petkov wrote:
> On Thu, Aug 15, 2019 at 05:46:46PM +0800, Rahul Tanwar wrote:
>> This patch adds a new variant of Intel Atom Airmont CPU model used in a
>> network processor SoC named Lightning Mountain.
>>
>> Signed-off-by: Rahul Tanwar <rahul.tanwar@linux.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 0278aa66ef62..cbbb8250370f 100644
>> --- a/arch/x86/include/asm/intel-family.h
>> +++ b/arch/x86/include/asm/intel-family.h
>> @@ -73,6 +73,7 @@
>>   
>>   #define INTEL_FAM6_ATOM_AIRMONT		0x4C /* Cherry Trail, Braswell */
>>   #define INTEL_FAM6_ATOM_AIRMONT_MID	0x5A /* Moorefield */
>> +#define INTEL_FAM6_ATOM_AIRMONT_NP	0x75 /* Lightning Mountain */
>>   
>>   #define INTEL_FAM6_ATOM_GOLDMONT	0x5C /* Apollo Lake */
>>   #define INTEL_FAM6_ATOM_GOLDMONT_X	0x5F /* Denverton */
>> -- 
> Also, in addition to what Thomas said, due to the fact that all the
> different groups within Intel are sending patches with model names,
> please synchronize that model naming and patch sending with Tony from
> now on:
>
> https://git.kernel.org/tip/5ed1c835ed8b522ce25071cc2d56a9a09bd5b59e
>
> He'll document the naming scheme and pay attention to what goes where so
> make sure you CC him, talk to him or have him in the loop, in general.
>
> Thx.
>

  reply	other threads:[~2019-08-16  3:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15  9:46 [PATCH 0/3] x86: cpu: Add new Airmont CPU model Rahul Tanwar
2019-08-15  9:46 ` [PATCH 1/3] x86: cpu: Use constant definitions for CPU type Rahul Tanwar
2019-08-15 10:31   ` Thomas Gleixner
2019-08-16  3:17     ` Tanwar, Rahul
2019-08-15  9:46 ` [PATCH 2/3] x86: cpu: Add new Intel Atom " Rahul Tanwar
2019-08-15 12:22   ` Borislav Petkov
2019-08-16  3:22     ` Tanwar, Rahul [this message]
2019-08-16  6:43       ` Borislav Petkov
2019-08-16  7:25         ` Tanwar, Rahul
2019-08-16  7:38           ` Borislav Petkov
2019-08-15  9:46 ` [PATCH 3/3] x86: arch: Add arch support for new Intel Atom CPU Rahul Tanwar

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=68ad47a7-ac6f-0a1b-0892-850bb95c002b@linux.intel.com \
    --to=rahul.tanwar@linux.intel.com \
    --cc=alan@linux.intel.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=bp@alien8.de \
    --cc=cheol.yong.kim@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=qi-ming.wu@intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rahul.tanwar@intel.com \
    --cc=ricardo.neri-calderon@linux.intel.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --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

Powered by JetHome