From: Denis Zaitsev <zzz@anda.ru>
To: linux-kernel@vger.kernel.org
Cc: linux-scsi@vger.kernel.org
Subject: [PATCH TRIVIAL] Compile error in 2.4.22 without PCI
Date: Wed, 15 Oct 2003 00:30:36 +0600 [thread overview]
Message-ID: <20031015003036.A10226@natasha.ward.six> (raw)
I have these warnings when I'm compiling 2.4.22 for a 486 EISA system:
aic7xxx_osm.c: In function `ahc_softc_comp':
aic7xxx_osm.c:1560: warning: implicit declaration of function `ahc_get_pci_bus'
aic7xxx_osm.c:1568: warning: implicit declaration of function `ahc_get_pci_slot'
And then the make finishes with an error, because these functions
really exist only if the PCI support is turned on.
The patch below fixes this. And the same patch fits for the 2.6
kernels. Please, apply it.
--- drivers/scsi/aic7xxx/aic7xxx_osm.c.orig 2003-09-15 01:56:14.000000000 +0600
+++ drivers/scsi/aic7xxx/aic7xxx_osm.c 2003-10-15 00:23:37.000000000 +0600
@@ -1552,6 +1552,7 @@ ahc_softc_comp(struct ahc_softc *lahc, s
/* Still equal. Sort by BIOS address, ioport, or bus/slot/func. */
switch (rvalue) {
+#ifdef CONFIG_PCI
case AHC_PCI:
{
char primary_channel;
@@ -1584,6 +1585,8 @@ ahc_softc_comp(struct ahc_softc *lahc, s
value = 1;
break;
}
+#endif
+#ifdef CONFIG_EISA
case AHC_EISA:
if ((rahc->flags & AHC_BIOS_ENABLED) != 0) {
value = rahc->platform_data->bios_address
@@ -1593,6 +1596,7 @@ ahc_softc_comp(struct ahc_softc *lahc, s
- lahc->bsh.ioport;
}
break;
+#endif
default:
panic("ahc_softc_sort: invalid bus type");
}
next reply other threads:[~2003-10-14 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 18:30 Denis Zaitsev [this message]
2003-10-17 12:33 ` [PATCH TRIVIAL] Compile error in 2.4.22 without PCI Christoph Hellwig
2003-10-18 20:52 ` Denis Zaitsev
-- strict thread matches above, loose matches on Subject: below --
2003-10-18 20:55 Denis Zaitsev
2003-10-31 21:29 Denis Zaitsev
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=20031015003036.A10226@natasha.ward.six \
--to=zzz@anda.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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