From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org
Subject: Re: [GIT PATCH] STAGING pull for .40
Date: Mon, 23 May 2011 16:00:33 -0700 [thread overview]
Message-ID: <20110523230033.GA26471@kroah.com> (raw)
In-Reply-To: <BANLkTi=vUXOfZ57CT7CtAjOzYReBnp=Vvg@mail.gmail.com>
On Mon, May 23, 2011 at 01:43:13PM -0700, Linus Torvalds wrote:
> On Mon, May 23, 2011 at 12:38 PM, Greg KH <greg@kroah.com> wrote:
> > Here is the big pull request for the staging tree for your .40 tree (or
> > 2.8.0, whatever you are wanting to rename it to.)
>
> Hmm. Doing my once-a-release "try to compile everything in staging
> after pulling from greg by using allyesconfig and also forcing all
> staging",
Ugh, I keep only testing 'allmodconfig' with all staging drivers, I'll
add this to my test build setup from now on.
> I get this:
>
> drivers/staging/brcm80211/brcmsmac/built-in.o:(.data+0xba0):
> multiple definition of `wl_msg_level'
> drivers/staging/brcm80211/brcmfmac/built-in.o:(.data+0x1a94): first
> defined here
>
> 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.
thanks,
greg k-h
next prev parent reply other threads:[~2011-05-23 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 19:38 [GIT PATCH] STAGING pull for .40 Greg KH
2011-05-23 20:43 ` Linus Torvalds
2011-05-23 23:00 ` Greg KH [this message]
2011-05-24 0:28 ` Franky (Zhenhui) Lin
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=20110523230033.GA26471@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=devel@linuxdriverproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.