public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Linux I2C <i2c@lm-sensors.org>
Subject: Re: [i2c] [GIT PULL] More i2c updates for 2.6.20
Date: Fri, 5 Jan 2007 18:34:39 +0100	[thread overview]
Message-ID: <20070105183439.29f41f0b.khali@linux-fr.org> (raw)
In-Reply-To: <20070104132806.79cf015e.khali@linux-fr.org>

Linus,

Please pull the i2c subsystem updates for Linux 2.6.20 from:

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

(This requests replaces the one from yesterday, as I received two urgent
fixes since then.)

These are late fixes that I want to have in 2.6.20, fixing compilation
breakage of the new i2c-pnx bus driver, a random oops in i2c-mv64xxx,
a bug in the m41t00 clock driver, and helping compatibility with
regards to planned i2c-core cleanups.

 Documentation/feature-removal-schedule.txt |   17 +++++++++++++++++
 MAINTAINERS                                |    6 ++++++
 drivers/i2c/busses/Kconfig                 |    9 ---------
 drivers/i2c/busses/i2c-mv64xxx.c           |    4 ++--
 drivers/i2c/busses/i2c-pnx.c               |    7 +------
 drivers/i2c/chips/m41t00.c                 |    1 +
 drivers/i2c/i2c-core.c                     |   28 ++++++++++++++++++++++++----
 7 files changed, 51 insertions(+), 21 deletions(-)

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

David Brownell:
      i2c: Migration aids for i2c_adapter.dev removal

Maxime Bizon:
      i2c-mv64xxx: Fix random oops at boot

Philippe De Muyter:
      i2c/m41t00: Do not forget to write year

Vitaly Wool:
      i2c-pnx: Fix interrupt handler, get rid of EARLY config option
      i2c-pnx: Add entry to MAINTAINERS

Thanks,
-- 
Jean Delvare

      reply	other threads:[~2007-01-05 17:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 12:28 [GIT PULL] More i2c updates for 2.6.20 Jean Delvare
2007-01-05 17:34 ` Jean Delvare [this message]

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=20070105183439.29f41f0b.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=i2c@lm-sensors.org \
    --cc=linux-kernel@vger.kernel.org \
    --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