From: Adrian Bunk <bunk@fs.tum.de>
To: Armin Schindler <armin@melware.de>
Cc: isdn4linux@listserv.isdn4linux.de,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
gpl-info@spellcast.com
Subject: [PATCH] let ISDN_DRV_SC depend on m
Date: Sat, 27 Sep 2003 00:50:21 +0200 [thread overview]
Message-ID: <20030926225021.GH2881@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.31.0309251331150.21651-100000@phoenix.one.melware.de>
On Thu, Sep 25, 2003 at 01:33:53PM +0200, Armin Schindler wrote:
> On Thu, 25 Sep 2003, Adrian Bunk wrote:
> > I got the link error below in 2.6.0-test5-mm4 (but it doesn't seem to be
> > specific to -mm).
> >
> > It seems some drivers under eicon/ and hardware/eicon/ use the same
> > symbols. Either some symbols should be renamed or Kconfig dependencies
> > should ensure that you can't build two such drivers statically into the
> > kernel at the same time.
>
> The legacy eicon driver in drivers/isdn/eicon is the old one and will be
> removed as soon as all features went to the new driver.
> Anyway this old driver was never meant to be non-module.
>
> This patch should do it.
Yes, thanks, this works. The similar patch for ISDN_DRV_SC below is
needed, too.
> Armin
cu
Adrian
--- linux-2.6.0-test5-mm4-no-smp-2.95/drivers/isdn/sc/Kconfig.old 2003-09-25 19:21:07.000000000 +0200
+++ linux-2.6.0-test5-mm4-no-smp-2.95/drivers/isdn/sc/Kconfig 2003-09-25 19:21:54.000000000 +0200
@@ -3,7 +3,7 @@
#
config ISDN_DRV_SC
tristate "Spellcaster support"
- depends on ISDN && ISA
+ depends on ISDN && ISA && m
help
This enables support for the Spellcaster BRI ISDN boards. This
driver currently builds only in a modularized version ( = code which
prev parent reply other threads:[~2003-09-26 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 10:15 2.6 eicon/ and hardware/eicon/ drivers using the same symbols Adrian Bunk
2003-09-25 11:33 ` [PATCH] " Armin Schindler
2003-09-25 11:38 ` Christoph Hellwig
2003-09-25 11:52 ` Armin Schindler
2003-09-26 22:50 ` Adrian Bunk [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=20030926225021.GH2881@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=armin@melware.de \
--cc=gpl-info@spellcast.com \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=linux-kernel@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®