public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	LM Sensors <lm-sensors@lm-sensors.org>
Subject: [GIT PULL] hwmon fixes for 2.6.33
Date: Sun, 10 Jan 2010 23:04:12 +0100	[thread overview]
Message-ID: <20100110230412.321d6c43@hyperion.delvare> (raw)

Hi Linus,

Please pull some hwmon subsystem fixes for Linux 2.6.33 from:

git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging.git hwmon-for-linus

The asus_atk0110 changes aren't fixes stricto sensu, however they
should make future bug investigation and fixes much easier so I still
think it's OK to merge it now.

 Documentation/hwmon/k10temp  |   17 ++-
 drivers/hwmon/Kconfig        |    2 +-
 drivers/hwmon/adt7462.c      |    2 +-
 drivers/hwmon/asus_atk0110.c |  289 ++++++++++++++++++++++++++++++++++--------
 drivers/hwmon/coretemp.c     |   16 ++-
 drivers/hwmon/k10temp.c      |   40 +++++-
 drivers/hwmon/k8temp.c       |    2 +-
 drivers/hwmon/sis5595.c      |    2 +-
 drivers/hwmon/via686a.c      |    2 +-
 drivers/hwmon/vt8231.c       |    2 +-
 10 files changed, 299 insertions(+), 75 deletions(-)

---------------

Clemens Ladisch (1):
      hwmon: (k10temp) Blacklist more family 10h processors

Luca Tettamanti (2):
      hwmon: (asus_atk0110) Refactor interface probe code
      hwmon: (asus_atk0110) Add debugfs interface

Márton Németh (1):
      hwmon: Make PCI device ids constant

Roger Blofeld (1):
      hwmon: (adt7462) Fix pin 28 monitoring

Yong Wang (1):
      hwmon: (coretemp) Fix TjMax for Atom N450/D410/D510 CPUs

Thanks,
-- 
Jean Delvare

             reply	other threads:[~2010-01-10 22:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-10 22:04 Jean Delvare [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-01-25 14:13 [GIT PULL] hwmon fixes for 2.6.33 Jean Delvare
2010-02-06 15:05 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=20100110230412.321d6c43@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.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