From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: [PATCH] i2c driver fixes for 2.6.0-test5
Date: Mon, 22 Sep 2003 16:30:16 -0700 [thread overview]
Message-ID: <1064273416272@kroah.com> (raw)
In-Reply-To: <10642734162392@kroah.com>
ChangeSet 1.1153.85.2, 2003/08/27 15:29:33-07:00, mds@paradyne.com
[PATCH] I2C: i2c-isa functionality
The "functionality" return was incorrectly removed for i2c-isa.c when porting to 2.5.
A driver that does nothing must return a 0 or else i2c-core assumes
0xffffffff (all functionality).
drivers/i2c/busses/i2c-isa.c | 9 +++++++++
1 files changed, 9 insertions(+)
diff -Nru a/drivers/i2c/busses/i2c-isa.c b/drivers/i2c/busses/i2c-isa.c
--- a/drivers/i2c/busses/i2c-isa.c Mon Sep 22 16:17:05 2003
+++ b/drivers/i2c/busses/i2c-isa.c Mon Sep 22 16:17:05 2003
@@ -30,10 +30,13 @@
#include <linux/errno.h>
#include <linux/i2c.h>
+static u32 isa_func(struct i2c_adapter *adapter);
+
/* This is the actual algorithm we define */
static struct i2c_algorithm isa_algorithm = {
.name = "ISA bus algorithm",
.id = I2C_ALGO_ISA,
+ .functionality = isa_func,
};
/* There can only be one... */
@@ -44,6 +47,12 @@
.algo = &isa_algorithm,
.name = "ISA main adapter",
};
+
+/* We can't do a thing... */
+static u32 isa_func(struct i2c_adapter *adapter)
+{
+ return 0;
+}
static int __init i2c_isa_init(void)
{
next prev parent reply other threads:[~2003-09-22 23:40 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 23:28 [BK PATCH] i2c driver fixes for 2.6.0-test5 Greg KH
2003-09-22 23:30 ` [PATCH] " Greg KH
2003-09-22 23:30 ` Greg KH [this message]
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
[not found] <10642734271572@kroah.com>
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-22 23:30 ` Greg KH
2003-09-23 8:16 ` Christoph Hellwig
2003-09-23 16:19 ` Greg KH
2003-09-23 16:22 ` Christoph Hellwig
2003-09-23 19:04 ` Greg KH
2003-09-23 19:08 ` Christoph Hellwig
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=1064273416272@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.com \
/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