From: Greg KH <greg@kroah.com>
To: torvalds@osdl.org, akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, sensors@Stimpy.netroedge.com
Subject: [BK PATCH] I2C update for 2.6.7-rc1
Date: Fri, 28 May 2004 14:59:08 -0700 [thread overview]
Message-ID: <20040528215908.GA13626@kroah.com> (raw)
Hi,
Here are some i2c driver fixes for 2.6.7-rc1. There is also a new i2c
chip driver in here. The majority of these patches have been in the
past few -mm releases.
Please pull from: bk://kernel.bkbits.net/gregkh/linux/i2c-2.6
Individual patches will follow, sent to the sensors and linux-kernel
lists.
thanks,
greg k-h
drivers/i2c/busses/Kconfig | 8
drivers/i2c/busses/i2c-ibm_iic.c | 48 +++-
drivers/i2c/busses/i2c-parport.h | 14 +
drivers/i2c/chips/Kconfig | 10 +
drivers/i2c/chips/Makefile | 1
drivers/i2c/chips/eeprom.c | 5
drivers/i2c/chips/max1619.c | 378 +++++++++++++++++++++++++++++++++++++++
drivers/i2c/i2c-core.c | 21 +-
8 files changed, 457 insertions(+), 28 deletions(-)
-----
<faikuygur:tnn.net>:
o I2C: use idr_get_new to allocate a bus id in drivers/i2c/i2c-core.c
<fishor:gmx.net>:
o I2C: add max1619 driver
Eugene Surovegin:
o I2C PPC4xx IIC driver: 0-length transaction temporary fix
o I2C PPC4xx IIC driver: fix debug build with gcc3
o I2C PPC4xx IIC driver: Kconfig cleanup
o I2C PPC4xx IIC driver: upgrade to new OCP infrastructre
Jean Delvare:
o I2C: i2c-parport: support the ADM1031 evaluation board
o I2C: Incomplete AT24RF08 corruption prevention in i2c eeprom
next reply other threads:[~2004-05-28 22:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 21:59 Greg KH [this message]
2004-05-28 22:00 ` [PATCH] I2C update for 2.6.7-rc1 Greg KH
2004-05-28 22:00 ` Greg KH
2004-05-28 22:00 ` Greg KH
2004-05-28 22:00 ` Greg KH
2004-05-28 22:00 ` Greg KH
2004-05-28 22:00 ` Greg KH
2004-05-28 22:00 ` Greg KH
2004-05-28 22:00 ` 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=20040528215908.GA13626@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@Stimpy.netroedge.com \
--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