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
On Tuesday 11 April 2006 18:42, Johannes Berg wrote:
On Tue, 2006-04-11 at 18:35 +0200, Michael Buesch wrote:
Sure. I would probably say that both m should conflict, too.
Nah, you probably want both m for testing.
I am OK with this, but it fucks up module autoloading.
But that is probably
Hi,
I looked into the symbol clash problems between bcm43xx and bcm43xx-d80211
you mentioned at the wireless summit.
Well, IMHO it is pretty hard to find a good solution to this.
The situation is: We have several nonstatic functions in the bcm driver. These
functions have the same name in the
