From: Greg KH <greg@kroah.com>
To: torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org, sensors@Stimpy.netroedge.com
Subject: [BK PATCH] i2c driver fixes for 2.6.0-test3
Date: Fri, 15 Aug 2003 11:32:07 -0700 [thread overview]
Message-ID: <20030815183207.GA3851@kroah.com> (raw)
Hi,
Here are some i2c driver fixes for 2.6.0-test3. They include a fix for
the i2c-dev driver that has gone into 2.4 and a pii4x bugfix from Tom
Rini. I've also added adapter and client "name" files in sysfs as the
driver core no longer supplies them.
Please pull from: bk://kernel.bkbits.net/gregkh/linux/i2c-2.5
thanks,
greg k-h
drivers/i2c/busses/i2c-nforce2.c | 29 ++++-----------------------
drivers/i2c/busses/i2c-piix4.c | 13 ++++++++++--
drivers/i2c/chips/Makefile | 4 ++-
drivers/i2c/chips/adm1021.c | 8 +++----
drivers/i2c/i2c-core.c | 28 ++++++++++++++++++++++++++
drivers/i2c/i2c-dev.c | 41 ++++++++++++++++++++++++---------------
6 files changed, 77 insertions(+), 46 deletions(-)
-----
<khali:linux-fr.org>:
o i2c: user/kernel bug and memory leak in i2c-dev
Greg Kroah-Hartman:
o I2C: add adapter and client name files as the driver core no longer provides them
o I2C: fix up the wording for the pii4x bugfix
o i2c: move w83481d to top of link order due to chip address takeover ability
o i2c: fix up "raw" printk() call
Mark M. Hoffman:
o I2C: i2c nforce2.c fixes
Rusty Lynch:
o I2C: bugfix for initialization bug in adm1021 driver
Tom Rini:
o I2C: Fix for i2c-piix4 with on some boards
next reply other threads:[~2003-08-15 18:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 18:32 Greg KH [this message]
2003-08-15 18:33 ` [PATCH] i2c driver changes 2.6.0-test3 Greg KH
2003-08-15 18:33 ` Greg KH
2003-08-15 18:33 ` Greg KH
2003-08-15 18:33 ` Greg KH
2003-08-15 18:33 ` Greg KH
2003-08-15 18:33 ` Greg KH
2003-08-15 18:33 ` Greg KH
2003-08-15 18:33 ` 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=20030815183207.GA3851@kroah.com \
--to=greg@kroah.com \
--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