public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux I2C <i2c@lm-sensors.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Ben Dooks <ben-linux@fluff.org>
Subject: [GIT PULL] i2c updates and fixes for 2.6.26
Date: Sun, 18 May 2008 22:51:54 +0200	[thread overview]
Message-ID: <20080518225154.1fa0681c@hyperion.delvare> (raw)

Linus,

Please pull the i2c subsystem updates and fixes for Linux 2.6.26 from:

git://jdelvare.pck.nerim.net/jdelvare-2.6 i2c-for-linus

(Note to other readers: please do NOT pull the whole kernel tree from
this location, my line wouldn't like it.)

You'll get the last pieces of the conversion of the device/driver
matching model of the i2c subsystem, blacklisting of 1 motherboard in
the i2c-nforce2 SMBus controller driver for safety reasons, and a few
random fixes.

Sorry for pushing this a bit late in the game, but I feel that if I
don't remove the old i2c device/driver matching mechanism now, more
drivers will start using it and it will be even mode work for me to
convert them all later.

 MAINTAINERS                                |    4 ++-
 arch/blackfin/mach-bf527/boards/ezkit.c    |    2 -
 arch/powerpc/platforms/pasemi/misc.c       |    7 +---
 drivers/i2c/busses/i2c-amd756.c            |    2 +-
 drivers/i2c/busses/i2c-nforce2.c           |   28 ++++++++++++++++---
 drivers/i2c/chips/max6875.c                |    3 --
 drivers/i2c/i2c-core.c                     |   22 +++------------
 drivers/media/video/cs5345.c               |    7 +++++
 drivers/media/video/cs53l32a.c             |   10 ++++++-
 drivers/media/video/cx18/cx18-i2c.c        |    9 +++---
 drivers/media/video/cx25840/cx25840-core.c |    7 +++++
 drivers/media/video/ivtv/ivtv-i2c.c        |   13 ++++-----
 drivers/media/video/m52790.c               |    9 +++++-
 drivers/media/video/msp3400-driver.c       |   17 ++++++++---
 drivers/media/video/saa7115.c              |   40 +++++++++++++++++++--------
 drivers/media/video/saa7127.c              |    9 +++++-
 drivers/media/video/saa717x.c              |    9 +++++-
 drivers/media/video/tuner-core.c           |   17 +++++++++++-
 drivers/media/video/upd64031a.c            |    6 ++++
 drivers/media/video/upd64083.c             |    6 ++++
 drivers/media/video/vp27smpx.c             |    9 +++++-
 drivers/media/video/wm8739.c               |    7 +++++
 drivers/media/video/wm8775.c               |    7 +++++
 include/linux/i2c.h                        |    7 +----
 include/linux/i2c/pcf857x.h                |    3 +-
 25 files changed, 180 insertions(+), 80 deletions(-)

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

Jean Delvare (8):
      i2c: New co-maintainer
      i2c-nforce2: Disable the second SMBus channel on the DFI Lanparty NF4 Expert
      i2c: Clean up Blackfin BF527 I2C device declarations
      i2c: Switch pasemi to the new device/driver matching scheme
      i2c: Convert remaining new-style drivers to use module aliasing
      i2c: Kill the old driver matching scheme
      i2c-amd756: Fix functionality flags
      i2c/max6875: Really prevent 24RF08 corruption

Thanks,
-- 
Jean Delvare

                 reply	other threads:[~2008-05-18 20:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080518225154.1fa0681c@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=ben-linux@fluff.org \
    --cc=i2c@lm-sensors.org \
    --cc=linux-kernel@vger.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