mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Rahul Tanwar <rahul.tanwar@linux.intel.com>
Cc: mingo@redhat.com, bp@alien8.de, 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 1/3] x86: cpu: Use constant definitions for CPU type
Date: Thu, 15 Aug 2019 12:31:49 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1908151226580.1923@nanos.tec.linutronix.de> (raw)
In-Reply-To: <bb09309eb9b4de8b8eff83d00d34c135b048fe25.1565856842.git.rahul.tanwar@linux.intel.com>

Rahul,

On Thu, 15 Aug 2019, Rahul Tanwar wrote:

Please use the proper prefix for your patches. x86 uses

x86/subsystem: not x86: subsystem:

> This patch replaces direct values usage with constant definitions usage
> when access CPU models.

Please do not use 'This patch'. We already know that this is a patch
otherwise you wouldn't have sent it with [PATCH] on the subject line,
right?

See Documentation/process/submitting-patches.rst and search for 'This
patch'.

> Signed-off-by: Rahul Tanwar <rahul.tanwar@linux.intel.com>
> Suggested-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> ---
>  arch/x86/kernel/cpu/intel.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/intel.c
> index 8d6d92ebeb54..0419fba1ea56 100644
> --- a/arch/x86/kernel/cpu/intel.c
> +++ b/arch/x86/kernel/cpu/intel.c
> @@ -265,9 +265,9 @@ static void early_init_intel(struct cpuinfo_x86 *c)
>  	/* Penwell and Cloverview have the TSC which doesn't sleep on S3 */
>  	if (c->x86 == 6) {
>  		switch (c->x86_model) {
> -		case 0x27:	/* Penwell */
> -		case 0x35:	/* Cloverview */
> -		case 0x4a:	/* Merrifield */
> +		case INTEL_FAM6_ATOM_SALTWELL_MID:	/* Penwell */
> +		case INTEL_FAM6_ATOM_SALTWELL_TABLET:	/* Cloverview */
> +		case INTEL_FAM6_ATOM_SILVERMONT_MID:	/* Merrifield */

Are these comments really still useful now that the defines are used? I
don't think so.

Thanks,

	tglx

  reply	other threads:[~2019-08-15 10:32 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 [this message]
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
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=alpine.DEB.2.21.1908151226580.1923@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --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=rahul.tanwar@linux.intel.com \
    --cc=ricardo.neri-calderon@linux.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

all inboxes | Powered by JetHome®