public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: torvalds@osdl.org, akpm@osdl.org
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [BK PATCH] More I2C patches for 2.6.12-rc1
Date: Fri, 1 Apr 2005 12:03:24 -0800	[thread overview]
Message-ID: <20050401200324.GA12854@kroah.com> (raw)

Hi,

I messed up on the last batch of i2c patches, and forgot 3 of them that
I had accepted, and were in my trees, but didn't get copied into the
tree that I sent for you to pull from.  All 3 of them are bugfixes.

Please pull from:
	bk://kernel.bkbits.net/gregkh/linux/i2c-2.6

Patches will be posted to linux-kernel and sensors as a follow-up thread
for those who want to see them.

thanks,

greg k-h

 drivers/i2c/chips/adm1021.c  |    2 +
 drivers/i2c/chips/adm1025.c  |   12 +++++++++
 drivers/i2c/chips/adm1026.c  |   55 ++++++++++++++-----------------------------
 drivers/i2c/chips/adm1031.c  |   23 +++++++----------
 drivers/i2c/chips/asb100.c   |   25 +++++++++++++++++--
 drivers/i2c/chips/ds1621.c   |    6 +++-
 drivers/i2c/chips/fscher.c   |   34 ++++++++++++++++++++------
 drivers/i2c/chips/fscpos.c   |   18 ++++++++++----
 drivers/i2c/chips/gl518sm.c  |   25 +++++++++++++++----
 drivers/i2c/chips/gl520sm.c  |   43 ++++++++++++++++++++++-----------
 drivers/i2c/chips/it87.c     |   44 +++++++++++++++++++++++++++++-----
 drivers/i2c/chips/lm63.c     |   19 +++++++++++++-
 drivers/i2c/chips/lm75.c     |    3 ++
 drivers/i2c/chips/lm77.c     |   21 +++++++++++++---
 drivers/i2c/chips/lm78.c     |   30 +++++++++++++++++++++--
 drivers/i2c/chips/lm80.c     |   16 ++++++++++--
 drivers/i2c/chips/lm83.c     |    3 ++
 drivers/i2c/chips/lm85.c     |   44 ++++++++++++----------------------
 drivers/i2c/chips/lm87.c     |   31 +++++++++++++++++++++---
 drivers/i2c/chips/lm90.c     |   14 +++++++++-
 drivers/i2c/chips/lm92.c     |   10 ++++++-
 drivers/i2c/chips/max1619.c  |    3 ++
 drivers/i2c/chips/pc87360.c  |   29 ++++++++++++++++++++++
 drivers/i2c/chips/pcf8574.c  |   27 +++++++--------------
 drivers/i2c/chips/pcf8591.c  |    6 +++-
 drivers/i2c/chips/sis5595.c  |   28 +++++++++++++++++++--
 drivers/i2c/chips/smsc47m1.c |   24 ++++++++++++++----
 drivers/i2c/chips/via686a.c  |   21 +++++++++++++++-
 drivers/i2c/chips/w83627hf.c |   32 ++++++++++++++++++++++++-
 drivers/i2c/chips/w83781d.c  |   29 ++++++++++++++++++++--
 drivers/i2c/i2c-core.c       |   19 --------------
 include/linux/i2c.h          |   10 ++++++-
 32 files changed, 516 insertions(+), 190 deletions(-)
-----


Jean Delvare:
  o I2C: Fix a common race condition in hardware monitoring
  o I2C: Move functionality handling from i2c-core to i2c.h
  o I2C: pcf8574 doesn't need a lock


             reply	other threads:[~2005-04-01 20:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-01 20:03 Greg KH [this message]
2005-04-01 20:04 ` [PATCH] I2C: pcf8574 doesn't need a lock Greg KH
2005-04-01 20:04   ` [PATCH] I2C: Move functionality handling from i2c-core to i2c.h Greg KH
2005-04-01 20:04     ` [PATCH] I2C: Fix a common race condition in hardware monitoring Greg KH

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=20050401200324.GA12854@kroah.com \
    --to=gregkh@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=torvalds@osdl.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