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 fixes for 2.6.10-rc1
Date: Thu, 19 May 2005 06:25:22 +0000	[thread overview]
Message-ID: <11003020053782@kroah.com> (raw)
In-Reply-To: <11003020054093@kroah.com>

ChangeSet 1.2094, 2004/11/12 11:40:22-08:00, greg@kroah.com

I2C: fix up rtc8564 which should not have been changed in my previous cleanups.

This fixes a reported oops.

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>


 drivers/i2c/chips/rtc8564.c |    3 +++
 1 files changed, 3 insertions(+)


diff -Nru a/drivers/i2c/chips/rtc8564.c b/drivers/i2c/chips/rtc8564.c
--- a/drivers/i2c/chips/rtc8564.c	2004-11-12 15:22:45 -08:00
+++ b/drivers/i2c/chips/rtc8564.c	2004-11-12 15:22:45 -08:00
@@ -66,8 +66,11 @@
 
 static struct i2c_client_address_data addr_data = {
 	.normal_i2c		= normal_addr,
+	.normal_i2c_range	= ignore,
 	.probe			= ignore,
+	.probe_range		= ignore,
 	.ignore			= ignore,
+	.ignore_range		= ignore,
 	.force			= ignore,
 };
 


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 fixes for 2.6.10-rc1
Date: Fri, 12 Nov 2004 15:26:45 -0800	[thread overview]
Message-ID: <11003020053782@kroah.com> (raw)
In-Reply-To: <11003020054093@kroah.com>

ChangeSet 1.2094, 2004/11/12 11:40:22-08:00, greg@kroah.com

I2C: fix up rtc8564 which should not have been changed in my previous cleanups.

This fixes a reported oops.

Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>


 drivers/i2c/chips/rtc8564.c |    3 +++
 1 files changed, 3 insertions(+)


diff -Nru a/drivers/i2c/chips/rtc8564.c b/drivers/i2c/chips/rtc8564.c
--- a/drivers/i2c/chips/rtc8564.c	2004-11-12 15:22:45 -08:00
+++ b/drivers/i2c/chips/rtc8564.c	2004-11-12 15:22:45 -08:00
@@ -66,8 +66,11 @@
 
 static struct i2c_client_address_data addr_data = {
 	.normal_i2c		= normal_addr,
+	.normal_i2c_range	= ignore,
 	.probe			= ignore,
+	.probe_range		= ignore,
 	.ignore			= ignore,
+	.ignore_range		= ignore,
 	.force			= ignore,
 };
 


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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-12 23:26 [BK PATCH] I2C fixes for 2.6.10-rc1 Greg KH
2005-05-19  6:25 ` Greg KH
2004-11-12 23:26 ` [PATCH] " Greg KH
2005-05-19  6:25   ` Greg KH
2004-11-12 23:26   ` Greg KH [this message]
2005-05-19  6:25     ` Greg KH
2004-11-12 23:26     ` Greg KH
2005-05-19  6:25       ` Greg KH
2004-11-12 23:26       ` Greg KH
2005-05-19  6:25         ` 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=11003020053782@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.