From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@osdl.org>,
James.Bottomley@SteelEye.com,
David Hinds <dahinds@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: [patch] 2.6.7-mm2: fdomain_cs needs unknown symbols
Date: Thu, 24 Jun 2004 21:16:18 +0200 [thread overview]
Message-ID: <20040624191617.GB26669@fs.tum.de> (raw)
In-Reply-To: <20040624014655.5d2a4bfb.akpm@osdl.org>
On Thu, Jun 24, 2004 at 01:46:55AM -0700, Andrew Morton wrote:
>...
> All 195 patches:
>...
> bk-scsi.patch
>...
This makes two functions in drivers/scsi/fdomain.c static that are
required in fdomain_cs.o:
<-- snip -->
WARNING: /lib/modules/2.6.7-mm2/kernel/drivers/scsi/pcmcia/fdomain_cs.ko
needs unknown symbol fdomain_16x0_bus_reset
WARNING: /lib/modules/2.6.7-mm2/kernel/drivers/scsi/pcmcia/fdomain_cs.ko
needs unknown symbol fdomain_setup
<-- snip -->
Although I agree that the way fdomain_cs.o is built is too ugly for
words, I'd suggest the following patch that revert these static's:
--- linux-2.6.7-mm2-modular/drivers/scsi/fdomain.c.old 2004-06-24 21:04:56.000000000 +0200
+++ linux-2.6.7-mm2-modular/drivers/scsi/fdomain.c 2004-06-24 21:07:17.000000000 +0200
@@ -418,7 +418,7 @@
static irqreturn_t do_fdomain_16x0_intr( int irq, void *dev_id,
struct pt_regs * regs );
-static int fdomain_16x0_bus_reset(struct scsi_cmnd *SCpnt);
+int fdomain_16x0_bus_reset(struct scsi_cmnd *SCpnt);
/* Allow insmod parameters to be like LILO parameters. For example:
insmod fdomain fdomain=0x140,11 */
@@ -555,7 +555,7 @@
printk( "\n" );
}
-static int __init fdomain_setup(char *str)
+int __init fdomain_setup(char *str)
{
int ints[4];
@@ -1541,7 +1541,7 @@
return SUCCESS;
}
-static int fdomain_16x0_bus_reset(struct scsi_cmnd *SCpnt)
+int fdomain_16x0_bus_reset(struct scsi_cmnd *SCpnt)
{
outb( 1, SCSI_Cntl_port );
do_pause( 2 );
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:[~2004-06-24 19:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 8:46 2.6.7-mm2 Andrew Morton
2004-06-24 9:39 ` 2.6.7-mm2 Russell King
2004-06-24 13:28 ` 2.6.7-mm2 Felipe Alfaro Solana
2004-06-24 10:33 ` 2.6.7-mm2 Andrew Morton
2004-06-24 11:43 ` 2.6.7-mm2 Angelo Dell'Aera
2004-06-24 17:28 ` 2.6.7-mm2 Norberto Bensa
2004-06-24 13:20 ` 2.6.7-mm2 Jari Ruusu
2004-06-24 15:04 ` 2.6.7-mm2 Roman Zippel
2004-06-24 18:00 ` 2.6.7-mm2 Valdis.Kletnieks
2004-06-24 14:25 ` 2.6.7-mm2 Coywolf Qi Hunt
2004-06-25 5:51 ` [PATCH] (2.6.7-mm2) kbuild distclean srctree fix ii Coywolf Qi Hunt
2004-06-24 17:46 ` 2.6.7-mm2 (compile stats) John Cherry
2004-06-24 19:16 ` Adrian Bunk [this message]
2004-06-24 20:57 ` 2.6.7-mm2 R. J. Wysocki
2004-06-24 21:38 ` 2.6.7-mm2 R. J. Wysocki
2004-06-24 21:50 ` 2.6.7-mm2 R. J. Wysocki
2004-06-25 5:21 ` 2.6.7-mm2 Andrew Morton
2004-06-25 10:48 ` 2.6.7-mm2 R. J. Wysocki
2004-06-24 20:59 ` 2.6.7-mm2: compile error SCHED_SMT + NUMA + gcc 2.95 Adrian Bunk
2004-06-24 21:24 ` Andrew Morton
2004-06-29 5:59 ` 2.6.7-mm2: random problems with mmap Peter Lundkvist
2004-06-29 6:50 ` Andrew Morton
2004-06-29 10:29 ` Jesper Juhl
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=20040624191617.GB26669@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=dahinds@users.sourceforge.net \
--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
all inboxes | Powered by JetHome®