From: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
To: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
Cc: linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Subject: Re: bcm43xx symbol clash problems
Date: Tue, 11 Apr 2006 18:35:03 +0200 [thread overview]
Message-ID: <200604111835.03948.mb@bu3sch.de> (raw)
In-Reply-To: <1144737580.4888.25.camel@localhost>
On Tuesday 11 April 2006 08:39, Johannes Berg wrote:
> On Mon, 2006-04-10 at 02:16 +0200, Michael Buesch wrote:
> > Does kbuild perhaps have some magic to handle that?
> >
> > This needs to be solved soon, but I have no idea how.
>
> You want to have bcm43xx and bcm43xx-dscape conflict anyway, since
> there's no point in building both into the kernel, only one can be bound
> to a device. Yes, I know one could still bind them manually, but that's
> about as icky as building them as modules imho. And whoever really needs
> a static kernel will not need both of them.
>
> I don't know how the Kconfig there is laid out, but wouldn't it be
> possible to make them conflict on both yes?
Sure. I would probably say that both m should conflict, too.
And one y and the other m, too.
This can be done with ugly "depends" statements.
--
Greetings Michael.
next prev parent reply other threads:[~2006-04-11 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 0:16 bcm43xx symbol clash problems Michael Buesch
[not found] ` <200604100216.21571.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-04-11 6:39 ` Johannes Berg
2006-04-11 16:35 ` Michael Buesch [this message]
[not found] ` <200604111835.03948.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-04-11 16:42 ` Johannes Berg
2006-04-11 16:59 ` Michael Buesch
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=200604111835.03948.mb@bu3sch.de \
--to=mb-fseuscv1ubazqb+pc5nmwq@public.gmane.org \
--cc=bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.