linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Andrew Morton <akpm@digeo.com>
Cc: Alistair Strachan <alistair@devzero.co.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.67-mm2
Date: 13 Apr 2003 16:45:24 -0400	[thread overview]
Message-ID: <1050266723.767.1.camel@localhost> (raw)
In-Reply-To: <20030413130543.081c80fd.akpm@digeo.com>

On Sun, 2003-04-13 at 16:05, Andrew Morton wrote:

> It's a bk bug.  This might make it boot:

Yah, I needed a similar patch to make 2.5.67-mm2 boot.  Not sure if its
hiding the real problem or not, but it works.

Note the difference between mine and your's, though.  I think you need
it.

	Robert Love


 drivers/base/class.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)


diff -urN linux-2.5.67/drivers/base/class.c linux/drivers/base/class.c
--- linux-2.5.67/drivers/base/class.c	2003-04-07 13:33:00.000000000 -0400
+++ linux/drivers/base/class.c	2003-04-13 16:32:52.000000000 -0400
@@ -103,12 +105,12 @@
 	struct device_class * cls = get_devclass(drv->devclass);
 	int error = 0;
 
-	if (cls) {
+	if (cls && &cls->subsys) {
 		down_write(&cls->subsys.rwsem);
 		pr_debug("device class %s: adding driver %s:%s\n",
 			 cls->name,drv->bus->name,drv->name);
 		error = devclass_drv_link(drv);
-		
+
 		if (!error)
 			list_add_tail(&drv->class_list,&cls->drivers.list);
 		up_write(&cls->subsys.rwsem);




  reply	other threads:[~2003-04-13 20:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-13 19:59 2.5.67-mm2 Alistair Strachan
2003-04-13 20:05 ` 2.5.67-mm2 Andrew Morton
2003-04-13 20:45   ` Robert Love [this message]
2003-04-14  0:49     ` 2.5.67-mm2 Greg KH
2003-04-14 18:21       ` 2.5.67-mm2 Greg KH
2003-04-14 19:33         ` 2.5.67-mm2 Alistair Strachan
2003-04-14 22:32         ` 2.5.67-mm2 Robert Love
2003-04-14  0:36   ` 2.5.67-mm2 Alistair Strachan
  -- strict thread matches above, loose matches on Subject: below --
2003-04-13  3:46 2.5.67-mm2 Shane Shrybman
2003-04-13  2:17 2.5.67-mm2 Shane Shrybman
2003-04-13  3:54 ` 2.5.67-mm2 Joshua Kwan
2003-04-13 11:12 ` 2.5.67-mm2 Felipe Alfaro Solana
2003-04-13  1:08 2.5.67-mm2 Andrew Morton
2003-04-13  1:55 ` 2.5.67-mm2 Felipe Alfaro Solana
2003-04-13  3:03   ` 2.5.67-mm2 Jeremy Hall
2003-04-13  3:10     ` 2.5.67-mm2 Andrew Morton
2003-04-13  3:54       ` 2.5.67-mm2 Jeremy Hall
2003-04-13  4:22         ` 2.5.67-mm2 Jeremy Hall
2003-04-13  4:32           ` 2.5.67-mm2 Andrew Morton
2003-04-13  3:14     ` 2.5.67-mm2 William Lee Irwin III
2003-04-13  3:50       ` 2.5.67-mm2 Jeremy Hall
2003-04-13  4:42         ` 2.5.67-mm2 Andrew Morton
2003-04-13  7:38           ` 2.5.67-mm2 Joshua Kwan
2003-04-13 19:02           ` 2.5.67-mm2 J Sloan
2003-04-13  3:17   ` 2.5.67-mm2 Valdis.Kletnieks
2003-04-13 11:15     ` 2.5.67-mm2 Felipe Alfaro Solana
2003-04-13  8:11   ` 2.5.67-mm2 Russell King
2003-04-13 13:12 ` 2.5.67-mm2 Ingo Oeser
2003-04-13 14:54   ` 2.5.67-mm2 Arjan van de Ven
2003-04-14  6:24     ` 2.5.67-mm2 Denis Vlasenko
2003-04-14  8:49       ` 2.5.67-mm2 Arjan van de Ven
2003-04-14 17:48 ` 2.5.67-mm2 Joel Becker
2003-04-14 21:31   ` 2.5.67-mm2 Andrew Morton
2003-04-14 21:34     ` 2.5.67-mm2 Randy.Dunlap

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=1050266723.767.1.camel@localhost \
    --to=rml@tech9.net \
    --cc=akpm@digeo.com \
    --cc=alistair@devzero.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).