All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: [PATCH] I2C update for 2.6.7-rc1
Date: Thu, 19 May 2005 06:25:00 +0000	[thread overview]
Message-ID: <1085781643301@kroah.com> (raw)
In-Reply-To: <10857816433753@kroah.com>
In-Reply-To: <1085781643100@kroah.com>

ChangeSet 1.1717.6.26, 2004/05/19 00:25:54-07:00, ebs@ebshome.net

[PATCH] I2C PPC4xx IIC driver: Kconfig cleanup

this patch renames Kconfig entry for PPC4xx IIC driver making it more clear and
also adds a help text.


 drivers/i2c/busses/Kconfig |    8 +++++++-
 1 files changed, 7 insertions(+), 1 deletion(-)


diff -Nru a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
--- a/drivers/i2c/busses/Kconfig	Fri May 28 14:52:22 2004
+++ b/drivers/i2c/busses/Kconfig	Fri May 28 14:52:22 2004
@@ -118,8 +118,14 @@
 	  will be called i2c-i810.
 
 config I2C_IBM_IIC
-	tristate "IBM IIC I2C"
+	tristate "IBM PPC 4xx on-chip I2C interface"
 	depends on IBM_OCP && I2C
+	help
+	  Say Y here if you want to use IIC peripheral found on 
+	  embedded IBM PPC 4xx based systems. 
+
+	  This driver can also be built as a module.  If so, the module
+	  will be called i2c-ibm_iic.
 
 config I2C_IOP3XX
 	tristate "Intel XScale IOP3xx on-chip I2C interface"


WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: [PATCH] I2C update for 2.6.7-rc1
Date: Fri, 28 May 2004 15:00:43 -0700	[thread overview]
Message-ID: <1085781643301@kroah.com> (raw)
In-Reply-To: <10857816433753@kroah.com>

ChangeSet 1.1717.6.26, 2004/05/19 00:25:54-07:00, ebs@ebshome.net

[PATCH] I2C PPC4xx IIC driver: Kconfig cleanup

this patch renames Kconfig entry for PPC4xx IIC driver making it more clear and
also adds a help text.


 drivers/i2c/busses/Kconfig |    8 +++++++-
 1 files changed, 7 insertions(+), 1 deletion(-)


diff -Nru a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
--- a/drivers/i2c/busses/Kconfig	Fri May 28 14:52:22 2004
+++ b/drivers/i2c/busses/Kconfig	Fri May 28 14:52:22 2004
@@ -118,8 +118,14 @@
 	  will be called i2c-i810.
 
 config I2C_IBM_IIC
-	tristate "IBM IIC I2C"
+	tristate "IBM PPC 4xx on-chip I2C interface"
 	depends on IBM_OCP && I2C
+	help
+	  Say Y here if you want to use IIC peripheral found on 
+	  embedded IBM PPC 4xx based systems. 
+
+	  This driver can also be built as a module.  If so, the module
+	  will be called i2c-ibm_iic.
 
 config I2C_IOP3XX
 	tristate "Intel XScale IOP3xx on-chip I2C interface"


  parent reply	other threads:[~2005-05-19  6:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 21:59 [BK PATCH] I2C update for 2.6.7-rc1 Greg KH
2005-05-19  6:25 ` Greg KH
2004-05-28 22:00 ` [PATCH] " Greg KH
2005-05-19  6:25   ` Greg KH
2004-05-28 22:00   ` Greg KH
2005-05-19  6:25     ` Greg KH
2004-05-28 22:00     ` Greg KH
2004-05-28 22:00       ` Greg KH [this message]
2005-05-19  6:25         ` Greg KH
2004-05-28 22:00         ` Greg KH
2005-05-19  6:25           ` Greg KH
2004-05-28 22:00           ` Greg KH
2005-05-19  6:25             ` Greg KH
2004-05-28 22:00             ` Greg KH
2005-05-19  6:25               ` 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=1085781643301@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.