All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rudolf Marek <r.marek@assembler.cz>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] k8temp on K8 rev.F and rev.G: Testers wanted
Date: Fri, 09 Jan 2009 15:14:36 +0000	[thread overview]
Message-ID: <496769DC.5050608@assembler.cz> (raw)
In-Reply-To: <20090109160702.466b8a6f@hyperion.delvare>


Hi I have revG2 CPU. I will test it.

Rudolf

Jean Delvare wrote:
> Hi all,
>
> I am done reviewing and testing Andreas' k8temp patches. After some
> reorganization I came up with the following stack:
>
> http://khali.linux-fr.org/devel/linux-2.6/jdelvare-hwmon/hwmon-k8temp-01-warn-about-errata.patch
> http://khali.linux-fr.org/devel/linux-2.6/jdelvare-hwmon/hwmon-k8temp-02-fix-wrong-sensor-selection-for-revf-revg.patch
> http://khali.linux-fr.org/devel/linux-2.6/jdelvare-hwmon/hwmon-k8temp-03-fix-temperature-reporting-for-most-revg.patch
>
> These are in linux-next at the moment, and I'd like to push them to
> Linus quickly. But I do not own any rev.F nor rev.G CPU myself, so I
> couldn't really test the patches, other than ensure that they do not
> cause a regression on earlier K8 CPUs.
>
> So this is a call to owners of rev.F and rev.G K8 CPUs, to try these
> patches and report how they are doing. There's also a standalone
> version of the updated driver at:
>   http://jdelvare.pck.nerim.net/sensors/k8temp/
> if it is easier for you.
>
> Thanks,
>   


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  reply	other threads:[~2009-01-09 15:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-09 15:07 [lm-sensors] k8temp on K8 rev.F and rev.G: Testers wanted Jean Delvare
2009-01-09 15:14 ` Rudolf Marek [this message]
2009-01-09 16:42 ` Daimonos Tereutes
2009-01-09 17:10 ` Jean Delvare
2009-01-11  9:45 ` Hans de Goede

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=496769DC.5050608@assembler.cz \
    --to=r.marek@assembler.cz \
    --cc=lm-sensors@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.