From: Adrian Bunk <bunk@fs.tum.de>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Atul Mukker <Atul.Mukker@lsil.com>,
linux-megaraid-devel@dell.com, linux-kernel@vger.kernel.org
Subject: [patch] Re: 2.4.23-pre7: build error with both megaraid drivers enabled
Date: Sat, 11 Oct 2003 17:30:04 +0200 [thread overview]
Message-ID: <20031011153004.GC25478@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0310110946070.7261-100000@iguana.domsch.com>
On Sat, Oct 11, 2003 at 09:48:08AM -0500, Matt Domsch wrote:
> > I get the following build error when trying to compile both megaraid
> > drivers statically into the kernel:
>
> They both drive the same hardware, so this isn't such a good idea. One or
> the other, but not both please, at least not built-in. Both as modules
> should be fine, you'll only ever load one. It's not surprising that a few
> functions are named the same between both.
This should be expressed through the Config.in dependencies, e.g. as
follows:
--- linux-2.4.23-pre7-full/drivers/scsi/Config.in.old 2003-10-11 17:00:47.000000000 +0200
+++ linux-2.4.23-pre7-full/drivers/scsi/Config.in 2003-10-11 17:24:00.000000000 +0200
@@ -67,7 +67,12 @@
dep_tristate 'Always IN2000 SCSI support' CONFIG_SCSI_IN2000 $CONFIG_SCSI
dep_tristate 'AM53/79C974 PCI SCSI support' CONFIG_SCSI_AM53C974 $CONFIG_SCSI $CONFIG_PCI
dep_tristate 'AMI MegaRAID support' CONFIG_SCSI_MEGARAID $CONFIG_SCSI
-dep_tristate 'AMI MegaRAID2 support' CONFIG_SCSI_MEGARAID2 $CONFIG_SCSI
+if [ "$CONFIG_SCSI_MEGARAID" != "y" ]; then
+ define_tristate CONFIG_SCSI_MEGARAID2_DEP $CONFIG_SCSI
+else
+ define_tristate CONFIG_SCSI_MEGARAID2_DEP m $CONFIG_SCSI
+fi
+dep_tristate 'AMI MegaRAID2 support' CONFIG_SCSI_MEGARAID2 $CONFIG_SCSI_MEGARAID2_DEP
dep_tristate 'BusLogic SCSI support' CONFIG_SCSI_BUSLOGIC $CONFIG_SCSI
if [ "$CONFIG_SCSI_BUSLOGIC" != "n" ]; then
> Thanks,
> Matt
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-10-11 15:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 0:52 Linux 2.4.23-pre7 Marcelo Tosatti
2003-10-10 15:59 ` Olaf Hering
2003-10-11 1:58 ` GOTO Masanori
2003-10-10 16:23 ` Linux 2.4.23-pre7 (irda compile fixes) Olaf Hering
2003-10-11 19:16 ` David S. Miller
2003-10-11 14:44 ` 2.4.23-pre7: build error with both megaraid drivers enabled Adrian Bunk
2003-10-11 14:48 ` Matt Domsch
2003-10-11 15:30 ` Adrian Bunk [this message]
2003-10-11 15:53 ` [patch] " Matt Domsch
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=20031011153004.GC25478@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=Atul.Mukker@lsil.com \
--cc=Matt_Domsch@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-megaraid-devel@dell.com \
--cc=marcelo.tosatti@cyclades.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox