From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: [PATCH] i2c driver changes for 2.5.66
Date: Mon, 24 Mar 2003 17:38 -0800 [thread overview]
Message-ID: <10485563201543@kroah.com> (raw)
In-Reply-To: <10485563193095@kroah.com>
ChangeSet 1.889.357.4, 2003/03/21 16:00:39-08:00, greg@kroah.com
i2c: add struct device to i2c_client structure
Not quite ready to hook it up to the driver core yet.
include/linux/i2c.h | 3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
diff -Nru a/include/linux/i2c.h b/include/linux/i2c.h
--- a/include/linux/i2c.h Mon Mar 24 17:28:24 2003
+++ b/include/linux/i2c.h Mon Mar 24 17:28:24 2003
@@ -170,8 +170,9 @@
void *data; /* for the clients */
int usage_count; /* How many accesses currently */
/* to the client */
+ struct device dev; /* the device structure */
};
-
+#define to_i2c_client(d) container_of(d, struct i2c_client, dev)
/*
* The following structs are for those who like to implement new bus drivers:
next prev parent reply other threads:[~2003-03-25 1:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 1:35 [BK PATCH] i2c driver changes for 2.5.66 Greg KH
2005-05-19 6:23 ` Greg KH
2003-03-25 1:38 ` [PATCH] " Greg KH
2005-05-19 6:23 ` Greg KH
2003-03-25 1:38 ` Greg KH
2005-05-19 6:23 ` Greg KH
2003-03-25 1:38 ` Greg KH
2005-05-19 6:23 ` Greg KH
2003-03-25 1:38 ` Greg KH
2005-05-19 6:23 ` Greg KH
2003-03-25 1:38 ` Greg KH
2005-05-19 6:23 ` Greg KH
2003-03-25 1:38 ` Greg KH
2003-03-25 1:38 ` Greg KH [this message]
2003-03-25 1:38 ` Greg KH
2005-05-19 6:23 ` Greg KH
2003-03-25 1:38 ` Greg KH
2005-05-19 6:23 ` Greg KH
2003-03-25 1:38 ` Greg KH
2003-03-25 1:38 ` Greg KH
2003-03-25 1:38 ` Greg KH
2005-05-19 6:23 ` Greg KH
2003-03-25 1:38 ` Greg KH
2003-03-25 1:38 ` Greg KH
2003-03-25 1:38 ` Greg KH
2003-03-25 8:55 ` Russell King
2005-05-19 6:23 ` Russell King
2003-03-25 8:58 ` Russell King
2005-05-19 6:23 ` Russell King
2003-03-25 9:17 ` Jan Dittmer
2003-03-26 1:22 ` 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=10485563201543@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.