From: Jean Delvare <khali@linux-fr.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux I2C <linux-i2c@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] i2c fixes for 2.6.33
Date: Sat, 16 Jan 2010 21:02:18 +0100 [thread overview]
Message-ID: <20100116210218.35c9a21d@hyperion.delvare> (raw)
Hi Linus,
Please pull i2c subsystem fixes for Linux 2.6.33 from:
git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging.git i2c-for-linus
drivers/i2c/busses/i2c-ali1563.c | 8 ++++----
drivers/i2c/busses/i2c-pca-isa.c | 4 ++--
drivers/i2c/busses/i2c-pca-platform.c | 4 ++--
drivers/i2c/busses/i2c-piix4.c | 4 ++--
drivers/i2c/busses/i2c-viapro.c | 4 ++--
drivers/i2c/i2c-core.c | 7 ++++---
6 files changed, 16 insertions(+), 15 deletions(-)
---------------
Márton Németh (1):
i2c-ali1563: Remove sparse warnings
Roel Kluin (1):
i2c: Test off by one in {piix4,vt596}_transaction()
Thadeu Lima de Souza Cascardo (1):
i2c: Do not use device name after device_unregister
Tobias Klauser (1):
i2c-core: Storage class should be before const qualifier
Wolfram Sang (1):
i2c/pca: Don't use *_interruptible
Thanks,
--
Jean Delvare
reply other threads:[~2010-01-16 20:02 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=20100116210218.35c9a21d@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).