public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Clemens Ladisch <clemens@ladisch.de>,
	"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hwmon: (k10temp) add support for AMD Family 12h/14h CPUs
Date: Thu, 17 Feb 2011 10:39:34 -0800	[thread overview]
Message-ID: <20110217183934.GB20387@ericsson.com> (raw)
In-Reply-To: <20110217190838.381962f6@endymion.delvare>

On Thu, Feb 17, 2011 at 01:08:38PM -0500, Jean Delvare wrote:
> On Thu, 17 Feb 2011 09:26:39 -0800, Guenter Roeck wrote:
> > On Thu, Feb 17, 2011 at 03:22:40AM -0500, Clemens Ladisch wrote:
> > > Add the PCI ID to support the internal temperature sensor of the
> > > AMD "Llano" and "Brazos" processor families.
> > > 
> > > Signed-off-by: Clemens Ladisch <clemens@ladisch.de>
> > 
> > Applied, thanks.
> > 
> > Since it meets the requirements for a stable patch, I applied it to the
> > patch list for 2.6.38 and added Cc: stable@kernel.org.
> 
> Can we have a sensors-detect patch too?
> 
Prepared that, but I am getting the following from the ddr3 patch.

prog/detect/sensors-detect
Useless use of private variable in void context at prog/detect/sensors-detect line 5287.

Code is
	} elsif ($device_type => 9 && $device_type <= 11) {

Should that be 
	} elsif ($device_type >= 9 && $device_type <= 11) {
instead ?

Odd, I didn't notice that before when I tried the ddr3 patch.

Guenter

  reply	other threads:[~2011-02-17 18:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17  8:22 [PATCH] hwmon: (k10temp) add support for AMD Family 12h/14h CPUs Clemens Ladisch
2011-02-17 17:26 ` Guenter Roeck
2011-02-17 18:08   ` Jean Delvare
2011-02-17 18:39     ` Guenter Roeck [this message]
2011-02-17 19:23       ` Jean Delvare

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=20110217183934.GB20387@ericsson.com \
    --to=guenter.roeck@ericsson.com \
    --cc=clemens@ladisch.de \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.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