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 driver changes for 2.5.72
Date: Thu, 19 May 2005 06:24:00 +0000	[thread overview]
Message-ID: <10559607081420@kroah.com> (raw)
In-Reply-To: <10559607081639@kroah.com>
In-Reply-To: <10559607053930@kroah.com>

ChangeSet 1.1318.3.5, 2003/06/16 11:32:48-07:00, greg@kroah.com

[PATCH] I2C: add lm78 chip to Makefile


 drivers/i2c/chips/Makefile |    1 +
 1 files changed, 1 insertion(+)


diff -Nru a/drivers/i2c/chips/Makefile b/drivers/i2c/chips/Makefile
--- a/drivers/i2c/chips/Makefile	Wed Jun 18 11:19:30 2003
+++ b/drivers/i2c/chips/Makefile	Wed Jun 18 11:19:30 2003
@@ -5,6 +5,7 @@
 obj-$(CONFIG_SENSORS_ADM1021)	+= adm1021.o
 obj-$(CONFIG_SENSORS_IT87)	+= it87.o
 obj-$(CONFIG_SENSORS_LM75)	+= lm75.o
+obj-$(CONFIG_SENSORS_LM78)	+= lm78.o
 obj-$(CONFIG_SENSORS_LM85)	+= lm85.o
 obj-$(CONFIG_SENSORS_VIA686A)	+= via686a.o
 obj-$(CONFIG_SENSORS_W83781D)	+= w83781d.o


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 driver changes for 2.5.72
Date: Wed, 18 Jun 2003 11:25:08 -0700	[thread overview]
Message-ID: <10559607081420@kroah.com> (raw)
In-Reply-To: <10559607081639@kroah.com>

ChangeSet 1.1318.3.5, 2003/06/16 11:32:48-07:00, greg@kroah.com

[PATCH] I2C: add lm78 chip to Makefile


 drivers/i2c/chips/Makefile |    1 +
 1 files changed, 1 insertion(+)


diff -Nru a/drivers/i2c/chips/Makefile b/drivers/i2c/chips/Makefile
--- a/drivers/i2c/chips/Makefile	Wed Jun 18 11:19:30 2003
+++ b/drivers/i2c/chips/Makefile	Wed Jun 18 11:19:30 2003
@@ -5,6 +5,7 @@
 obj-$(CONFIG_SENSORS_ADM1021)	+= adm1021.o
 obj-$(CONFIG_SENSORS_IT87)	+= it87.o
 obj-$(CONFIG_SENSORS_LM75)	+= lm75.o
+obj-$(CONFIG_SENSORS_LM78)	+= lm78.o
 obj-$(CONFIG_SENSORS_LM85)	+= lm85.o
 obj-$(CONFIG_SENSORS_VIA686A)	+= via686a.o
 obj-$(CONFIG_SENSORS_W83781D)	+= w83781d.o


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

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 18:24 [BK PATCH] i2c driver changes for 2.5.72 Greg KH
2005-05-19  6:24 ` Greg KH
2003-06-18 18:25 ` [PATCH] " Greg KH
2005-05-19  6:24   ` Greg KH
2003-06-18 18:25   ` Greg KH
2005-05-19  6:24     ` Greg KH
2003-06-18 18:25     ` Greg KH
2005-05-19  6:24       ` Greg KH
2003-06-18 18:25       ` Greg KH
2005-05-19  6:24         ` Greg KH
2003-06-18 18:25         ` Greg KH [this message]
2005-05-19  6:24           ` Greg KH
2003-06-18 18:25           ` Greg KH
2005-05-19  6:24             ` Greg KH
2003-06-18 18:25             ` Greg KH
2005-05-19  6:24               ` Greg KH
2003-06-18 18:25               ` Greg KH
2005-05-19  6:24                 ` Greg KH
2005-05-19  6:24   ` Greg KH
2005-05-19  6:24   ` Philip Pokorny
2005-05-19  6:24   ` Mark M. Hoffman
2005-05-19  6:24   ` Mark M. Hoffman
2005-05-19  6:24   ` Mark M. Hoffman
2005-05-19  6:24   ` Philip Pokorny
2005-05-19  6:24   ` Mark M. Hoffman
2005-05-19  6:24   ` Mark M. Hoffman
2005-05-19  6:24   ` Mark M. Hoffman
2005-05-19  6:24   ` Philip Pokorny
2005-05-19  6:24   ` Mark M. Hoffman
2005-05-19  6:24   ` Mark M. Hoffman
2005-05-19  6:24   ` Greg KH
2005-05-19  6:24   ` Mark D. Studebaker 

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=10559607081420@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.