public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andreas Herrmann <andreas.herrmann3@amd.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	cpufreq@vger.kernel.org, stable@kernel.org, "Langsdorf,
	Mark" <mark.langsdorf@amd.com>,
	linux-kernel@vger.kernel.org, davej@redhat.com
Subject: Re: [PATCH] x86: powernow-k8: ignore out-of-range PstateStatus value
Date: Fri, 21 Nov 2008 09:23:46 +0100	[thread overview]
Message-ID: <20081121082346.GK16242@elte.hu> (raw)
In-Reply-To: <20081121080841.GD10940@alberich.amd.com>


nice fix! A few minor nits:

> +			/* a workaround for family 11h erratum 311 might cause
> +			   an "out-of-range Pstate if the core is in Pstate-0 */

Please use the customary comment style:

  /*
   * Comment .....
   * ...... goes here:
   */

and since it's multi-line anyway, keep to the 80-col limit too please.

> diff --git a/arch/x86/kernel/cpu/cpufreq/powernow-k8.h b/arch/x86/kernel/cpu/cpufreq/powernow-k8.h
> index ab48cfe..4078f5d 100644
> --- a/arch/x86/kernel/cpu/cpufreq/powernow-k8.h
> +++ b/arch/x86/kernel/cpu/cpufreq/powernow-k8.h
> @@ -23,7 +23,9 @@ struct powernow_k8_data {
>          u32 exttype; /* extended interface = 1 */
>  
>  	/* keep track of the current fid / vid or pstate */
> -	u32 currvid, currfid, currpstate;
> +	u32 currvid, currfid;
> +	u32 currpstate;

Any reason why it has been moved to a separate line? (either split all 
fields or keep them all together)

> +#define INVALID_HW_PSTATE 0xff

Please use an enum, not a define in the middle of a struct.

Thanks,

        Ingo

  reply	other threads:[~2008-11-21  8:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07 15:08 [PATCH] x86: powernow-k8: ignore out-of-range PstateStatus value Andreas Herrmann
2008-11-21  8:08 ` Andreas Herrmann
2008-11-21  8:23   ` Ingo Molnar [this message]
2008-11-21 13:16     ` Andreas Herrmann
2008-11-21 15:12       ` Ingo Molnar
2008-11-21 13:49     ` [PATCH v2] " Andreas Herrmann

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=20081121082346.GK16242@elte.hu \
    --to=mingo@elte.hu \
    --cc=andreas.herrmann3@amd.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.langsdorf@amd.com \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.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