From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: [PATCH] i2c driver changes 2.6.0-test1
Date: Sat, 19 Jul 2003 08:54:50 -0700 [thread overview]
Message-ID: <105863009030@kroah.com> (raw)
In-Reply-To: <20030719155233.GA11754@kroah.com>
ChangeSet 1.1310.80.1, 2003/06/24 14:58:09-07:00, nikkne@hotpop.com
[PATCH] I2C: fix Kconfig info
drivers/i2c/Kconfig | 4 +---
1 files changed, 1 insertion(+), 3 deletions(-)
diff -Nru a/drivers/i2c/Kconfig b/drivers/i2c/Kconfig
--- a/drivers/i2c/Kconfig Sat Jul 19 08:48:43 2003
+++ b/drivers/i2c/Kconfig Sat Jul 19 08:48:43 2003
@@ -20,9 +20,7 @@
interfaces", below.
If you want I2C support, you should say Y here and also to the
- specific driver for your bus adapter(s) below. If you say Y to
- "/proc file system" below, you will then get a /proc interface which
- is documented in <file:Documentation/i2c/proc-interface>.
+ specific driver for your bus adapter(s) below.
This I2C support is also available as a module. If you want to
compile it as a module, say M here and read
WARNING: multiple messages have this Message-ID (diff)
From: greg@kroah.com (Greg KH)
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: [PATCH] i2c driver changes 2.6.0-test1
Date: Thu, 19 May 2005 06:24:05 +0000 [thread overview]
Message-ID: <105863009030@kroah.com> (raw)
In-Reply-To: <20030719155233.GA11754@kroah.com>
ChangeSet 1.1310.80.1, 2003/06/24 14:58:09-07:00, nikkne@hotpop.com
[PATCH] I2C: fix Kconfig info
drivers/i2c/Kconfig | 4 +---
1 files changed, 1 insertion(+), 3 deletions(-)
diff -Nru a/drivers/i2c/Kconfig b/drivers/i2c/Kconfig
--- a/drivers/i2c/Kconfig Sat Jul 19 08:48:43 2003
+++ b/drivers/i2c/Kconfig Sat Jul 19 08:48:43 2003
@@ -20,9 +20,7 @@
interfaces", below.
If you want I2C support, you should say Y here and also to the
- specific driver for your bus adapter(s) below. If you say Y to
- "/proc file system" below, you will then get a /proc interface which
- is documented in <file:Documentation/i2c/proc-interface>.
+ specific driver for your bus adapter(s) below.
This I2C support is also available as a module. If you want to
compile it as a module, say M here and read
next prev parent reply other threads:[~2003-07-19 15:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 15:52 [BK PATCH] i2c driver changes for 2.6.0-test1 Greg KH
2005-05-19 6:24 ` Greg KH
2003-07-19 15:54 ` Greg KH [this message]
2005-05-19 6:24 ` [PATCH] i2c driver changes 2.6.0-test1 Greg KH
2003-07-19 15:54 ` Greg KH
2005-05-19 6:24 ` Greg KH
2003-07-19 15:54 ` Greg KH
2005-05-19 6:24 ` Greg KH
2003-07-19 15:54 ` Greg KH
2005-05-19 6:24 ` Greg KH
2003-07-19 15:54 ` Greg KH
2005-05-19 6:24 ` Greg KH
2003-07-19 15:54 ` Greg KH
2005-05-19 6:24 ` Greg KH
2003-07-23 17:43 ` Marcelo Penna Guerra
2005-05-19 6:24 ` Marcelo Penna Guerra
2003-07-24 13:27 ` Greg KH
2005-05-19 6:24 ` 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=105863009030@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.