From: Keith Owens <kaos@ocs.com.au>
To: Adam Kropelin <akropel1@rochester.rr.com>
Cc: davej@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.1[345]-dj Add cpqarray_init() back into genhd.c
Date: Tue, 14 May 2002 12:24:23 +1000 [thread overview]
Message-ID: <6422.1021343063@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 13 May 2002 22:03:34 -0400." <20020514020334.GA24417@www.kroptech.com>
On Mon, 13 May 2002 22:03:34 -0400,
Adam Kropelin <akropel1@rochester.rr.com> wrote:
>In 2.5.13-dj1, the call to cpqarray_init() in drivers/block/genhd.c was
>dropped. I'm not sure what the intent was since the driver seems to work fine
>as a module. In case it was a mistake, here's a patch (against 2.5.15-dj1) to
>add it back in. Without it, cpqarray only works as a module. Works For Me (tm).
>
>--Adam
>
>--- linux-2.5.15-dj1-virgin/drivers/block/genhd.c Mon May 13 21:21:59 2002
>+++ linux-2.5.15-dj1/drivers/block/genhd.c Mon May 13 21:18:48 2002
>@@ -229,6 +229,9 @@
> /* This has to be done before scsi_dev_init */
> soc_probe();
> #endif
>+#ifdef CONFIG_BLK_CPQ_DA
>+ cpqarray_init();
>+#endif
> #ifdef CONFIG_NET
> net_dev_init();
> #endif
The real problem appears to be cpqarray.c, it wraps the init/exit code
in #ifdef MODULE, so the init code is only available to modules. I
think that cpqarray.c should remove the #ifdef MODULE and use the same
init mechanism as other drivers, including module_init/exit. I don't
have a card and the code is a mess so I am not going to attempt a patch.
next prev parent reply other threads:[~2002-05-14 2:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 2:03 Adam Kropelin
2002-05-14 2:24 ` Keith Owens [this message]
2002-05-14 2:49 ` Adam Kropelin
2002-05-14 3:31 ` Keith Owens
2002-05-14 11:38 ` Adam Kropelin
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=6422.1021343063@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=akropel1@rochester.rr.com \
--cc=davej@suse.de \
--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
all inboxes | Powered by JetHome®