From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, mac@melware.de,
isdn4linux@listserv.isdn4linux.de, kkeil@suse.de,
kai.germaschewski@gmx.de
Subject: [patch] 2.6.0-test11-mm1: isdn/eicon/eicon_mod.c doesn't compile
Date: Fri, 19 Dec 2003 17:58:38 +0100 [thread overview]
Message-ID: <20031219165837.GN12750@fs.tum.de> (raw)
In-Reply-To: <20031217014350.028460b2.akpm@osdl.org>
Hi Andrew,
I got the following compile error in 2.6.0-test11-mm1:
<-- snip -->
...
CC [M] drivers/isdn/eicon/eicon_mod.o
drivers/isdn/eicon/eicon_mod.c: In function `eicon_exit':
drivers/isdn/eicon/eicon_mod.c:1362: warning: implicit declaration of
function `mca_mark_as_unused'
drivers/isdn/eicon/eicon_mod.c: In function `eicon_mca_find_card':
drivers/isdn/eicon/eicon_mod.c:1500: warning: implicit declaration of
function `mca_find_unused_adapter'
drivers/isdn/eicon/eicon_mod.c:1502: `MCA_NOTFOUND' undeclared (first
use in this function)
drivers/isdn/eicon/eicon_mod.c:1502: (Each undeclared identifier is
reported only once
drivers/isdn/eicon/eicon_mod.c:1502: for each function it appears in.)
drivers/isdn/eicon/eicon_mod.c: In function `eicon_mca_probe':
drivers/isdn/eicon/eicon_mod.c:1558: warning: implicit declaration of
function `mca_read_stored_pos'
drivers/isdn/eicon/eicon_mod.c:1619: warning: implicit declaration of
function `mca_set_adapter_name'
drivers/isdn/eicon/eicon_mod.c:1622: warning: implicit declaration of
function `mca_mark_as_used'
make[3]: *** [drivers/isdn/eicon/eicon_mod.o] Error 1
<-- snip -->
The fix is simple:
--- linux-2.6.0-test11-mm1-modular-no-smp/drivers/isdn/eicon/eicon_mod.c.old 2003-12-19 17:26:56.000000000 +0100
+++ linux-2.6.0-test11-mm1-modular-no-smp/drivers/isdn/eicon/eicon_mod.c 2003-12-19 17:28:29.000000000 +0100
@@ -29,6 +29,7 @@
#include <linux/init.h>
#ifdef CONFIG_MCA
#include <linux/mca.h>
+#include <linux/mca-legacy.h>
#endif /* CONFIG_MCA */
#include "eicon.h"
Please apply
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-12-19 16:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 9:43 2.6.0-test11-mm1 Andrew Morton
2003-12-17 10:13 ` Question about UFS/UFS2 Niraj Kumar
2003-12-17 10:37 ` 2.6.0-test11-mm1 Andrew Walrond
2003-12-17 11:11 ` 2.6.0-test11-mm1 Christian Axelsson
2003-12-17 11:51 ` 2.6.0-test11-mm1 Andrew Morton
2003-12-18 3:24 ` 2.6.0-test11-mm1 Thomas Molina
2003-12-18 3:36 ` 2.6.0-test11-mm1 Andrew Morton
2003-12-19 18:21 ` 2.6.0-test11-mm1 Jens Axboe
2003-12-17 11:52 ` 2.6.0-test11-mm1 Andrew Morton
2003-12-17 13:30 ` 2.6.0-test11-mm1 Felipe Alfaro Solana
2003-12-17 11:57 ` UP build broken (Re: 2.6.0-test11-mm1) Dagfinn Ilmari Mannsåker
2003-12-17 11:55 ` Luiz Fernando Capitulino
2003-12-17 13:56 ` 2.6.0-test11-mm1 Zwane Mwaikambo
2003-12-17 18:22 ` 2.6.0-test11-mm1 Diego Calleja García
2003-12-17 22:01 ` 2.6.0-test11-mm1 Andrew Morton
2003-12-17 23:59 ` 2.6.0-test11-mm1 Paul Mackerras
2003-12-19 16:58 ` Adrian Bunk [this message]
2003-12-26 18:22 ` SUCCESS 2.6.0-test11-mm1 Matthias Urlichs
2003-12-26 19:15 ` Linus Torvalds
2003-12-28 21:59 ` Matthias Urlichs
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=20031219165837.GN12750@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@osdl.org \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=kai.germaschewski@gmx.de \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mac@melware.de \
/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®