linux-kernel - RE: [GIT PATCH] STAGING pull for .40

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 23 May 2011 17:28:54 -0700
From:	"Franky (Zhenhui) Lin" <frankyl@...adcom.com>
To:	"Greg KH" <greg@...ah.com>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>
cc:	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [GIT PATCH] STAGING pull for .40

On Mon, May 23, 2011 at 04:01 PM, Greg KH <greg@...ah.com> wrote:
> On Mon, May 23, 2011 at 01:43:13PM -0700, Linus Torvalds wrote:
> > which looks like another case of "can't compile two things both into
> > the kernel".
> >
> > Looks like the BRCMSMAC / BRCMFMAC drivers need to be mutually
> > exclusive. Something like
> >
> >   depends on m || (BRCMSMAC != y)
> >
> > for BRCMFMAC?
> >
> > Or they should just avoid using the same globally visible name.
> 
> Both probably.  I'll fix this up for the next set of staging fixes
> after
> you release -rc1.

Sorry about this. We have never compiled both modules with yesconfig to check for coexistence issue. We will add this to checklist from now on. And there should not be any coexistence problem for brcmsmac and brcmfmac. I will send out a patch for fixing this today.

Thanks,
Franky

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/