From: greg@kroah.com (Greg KH)
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: [PATCH] i2c driver changes for 2.5.66
Date: Thu, 19 May 2005 06:23:51 +0000 [thread overview]
Message-ID: <10485563181803@kroah.com> (raw)
In-Reply-To: <10485563161329@kroah.com>
In-Reply-To: <10485563223599@kroah.com>
ChangeSet 1.889.357.1, 2003/03/21 12:29:44-08:00, vandrove@vc.cvut.cz
[PATCH] Fix kobject_get oopses triggered by i2c in 2.5.65-bk
i2c initialization must not use module_init now, when it was converted
to the kobject interface. There are dozens of users which need it working
much sooner. i2c is subsystem after all, isn't it?
Fixes kernel oopses in kobject_get during system init which were happening
to me.
drivers/i2c/i2c-core.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -Nru a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
--- a/drivers/i2c/i2c-core.c Mon Mar 24 17:28:49 2003
+++ b/drivers/i2c/i2c-core.c Mon Mar 24 17:28:49 2003
@@ -675,7 +675,7 @@
bus_unregister(&i2c_bus_type);
}
-module_init(i2c_init);
+subsys_initcall(i2c_init);
module_exit(i2c_exit);
/* ----------------------------------------------------
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.66
Date: Mon, 24 Mar 2003 17:38 -0800 [thread overview]
Message-ID: <10485563181803@kroah.com> (raw)
In-Reply-To: <10485563161329@kroah.com>
ChangeSet 1.889.357.1, 2003/03/21 12:29:44-08:00, vandrove@vc.cvut.cz
[PATCH] Fix kobject_get oopses triggered by i2c in 2.5.65-bk
i2c initialization must not use module_init now, when it was converted
to the kobject interface. There are dozens of users which need it working
much sooner. i2c is subsystem after all, isn't it?
Fixes kernel oopses in kobject_get during system init which were happening
to me.
drivers/i2c/i2c-core.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -Nru a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
--- a/drivers/i2c/i2c-core.c Mon Mar 24 17:28:49 2003
+++ b/drivers/i2c/i2c-core.c Mon Mar 24 17:28:49 2003
@@ -675,7 +675,7 @@
bus_unregister(&i2c_bus_type);
}
-module_init(i2c_init);
+subsys_initcall(i2c_init);
module_exit(i2c_exit);
/* ----------------------------------------------------
next prev parent reply other threads:[~2005-05-19 6:23 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 [this message]
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
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=10485563181803@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.