From: Karsten Keil <kkeil@suse.de>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Adrian Bunk <bunk@fs.tum.de>,
isdn4linux@listserv.isdn4linux.de, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] ISDN PCBIT: #ifdef MODULE some code
Date: Sat, 16 Aug 2003 13:44:10 +0200 [thread overview]
Message-ID: <20030816114410.GA15437@pingi3.kke.suse.de> (raw)
In-Reply-To: <20030815184720.B0E502CE86@lists.samba.org>
On Sat, Aug 16, 2003 at 02:51:20AM +1000, Rusty Russell wrote:
> In message <20030728202500.GM25402@fs.tum.de> you write:
> > I got the following error at the final linkage of 2.6.0-test2 if
> > CONFIG_ISDN_DRV_PCBIT is compiled statically:
> >
> > <-- snip -->
> >
> > ...
> > LD .tmp_vmlinux1
> > ...
> > drivers/built-in.o(.exit.text+0xe183): In function `pcbit_exit':
> > : undefined reference to `pcbit_terminate'
> > make: *** [.tmp_vmlinux1] Error 1
>
> AFAICT This is also broken in 2.4.22-rc2, which makes me wonder if
> anyone actually cares about this driver?
>
> Taken anyway, for both.
It is used, I got some reports last year (but this card is only sold in
Portugal and is expensiv so far I know and so not so much people
using this card and linux).
Here 2 reasons why such thinks don't matter today:
1. 99% compile the ISDN stuff as module (and some parts are only work as
modules)
2. In 2.4 the exit function is removed at compile time, if not compiled as
modul.
I preparing lot of bugfixes for ISDN and 2.6, but testing needs much time and
many things are broken not only at compile time.
--
Karsten Keil
SuSE Labs
ISDN development
prev parent reply other threads:[~2003-08-16 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 20:25 [2.6 patch] ISDN PCBIT: #ifdef MODULE some code Adrian Bunk
2003-08-15 16:51 ` Rusty Russell
2003-08-15 20:46 ` Adrian Bunk
2003-08-16 11:44 ` Karsten Keil [this message]
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=20030816114410.GA15437@pingi3.kke.suse.de \
--to=kkeil@suse.de \
--cc=bunk@fs.tum.de \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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;
as well as URLs for NNTP newsgroup(s).