linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Henry Ptasinski <henryp@broadcom.com>
Cc: Greg KH <greg@kroah.com>, Stephen Rothwell <sfr@canb.auug.org.au>,
	driverdevel <devel@driverdev.osuosl.org>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"gregkh@suse.de" <gregkh@suse.de>,
	Brett Rudley <brudley@broadcom.com>,
	Nohee Ko <noheek@broadcom.com>
Subject: Re: [PATCH -next] staging: brcm80211 depends on MAC80211
Date: Tue, 21 Sep 2010 11:18:04 -0700	[thread overview]
Message-ID: <4C98F6DC.1070005@oracle.com> (raw)
In-Reply-To: <4C98F66C.809@broadcom.com>

On 09/21/10 11:16, Henry Ptasinski wrote:
> On 09/21/2010 11:06 AM, Greg KH wrote:
>> On Tue, Sep 21, 2010 at 10:23:23AM -0700, Henry Ptasinski wrote:
>>> On 09/21/2010 09:35 AM, Randy Dunlap wrote:
>>>> From: Randy Dunlap<randy.dunlap@oracle.com>
>>>>
>>>> Fix brcm890211 build: it should depend on MAC80211.
>>>> MAC80211 depends on CFG80211, which takes care of<regulatory_hint>
>>>> below.
>>>>
>>>> ERROR: "ieee80211_rx_irqsafe"
>>>> [drivers/staging/brcm80211/brcm80211.ko] undefined!
>>>> ERROR: "ieee80211_unregister_hw"
>>>> [drivers/staging/brcm80211/brcm80211.ko] undefined!
>>>> ERROR: "ieee80211_stop_queues"
>>>> [drivers/staging/brcm80211/brcm80211.ko] undefined!
>>>> ERROR: "ieee80211_wake_queues"
>>>> [drivers/staging/brcm80211/brcm80211.ko] undefined!
>>>> ERROR: "ieee80211_stop_tx_ba_cb_irqsafe"
>>>> [drivers/staging/brcm80211/brcm80211.ko] undefined!
>>>> ERROR: "ieee80211_tx_status_irqsafe"
>>>> [drivers/staging/brcm80211/brcm80211.ko] undefined!
>>>> ERROR: "ieee80211_register_hw"
>>>> [drivers/staging/brcm80211/brcm80211.ko] undefined!
>>>> ERROR: "regulatory_hint" [drivers/staging/brcm80211/brcm80211.ko]
>>>> undefined!
>>>> ERROR: "ieee80211_alloc_hw" [drivers/staging/brcm80211/brcm80211.ko]
>>>> undefined!
>>>> ERROR: "ieee80211_free_hw" [drivers/staging/brcm80211/brcm80211.ko]
>>>> undefined!
>>>> ERROR: "ieee80211_start_tx_ba_cb_irqsafe"
>>>> [drivers/staging/brcm80211/brcm80211.ko] undefined!
>>>>
>>>> Signed-off-by: Randy Dunlap<randy.dunlap@oracle.com>
>>>> Cc: Brett Rudley<brudley@broadcom.com>
>>>> Cc: Henry Ptasinski<henryp@broadcom.com>
>>>> Cc: Nohee Ko<noheek@broadcom.com>
>>>> ---
>>>>   drivers/staging/brcm80211/Kconfig |    2 +-
>>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> --- linux-next-20100921.orig/drivers/staging/brcm80211/Kconfig
>>>> +++ linux-next-20100921/drivers/staging/brcm80211/Kconfig
>>>> @@ -1,6 +1,6 @@
>>>>   menuconfig BRCM80211
>>>>       tristate "Broadcom 802.11 WLAN driver for bcm43xx chips"
>>>> -    depends on PCI&&   WLAN
>>>> +    depends on PCI&&   WLAN&&   MAC80211
>>>>       select WIRELESS_EXT
>>>>       select WEXT_PRIV
>>>>       default N
>>>>
>>>
>>> Actually, I think that should be something like:
>>>
>>> diff --git a/drivers/staging/brcm80211/Kconfig
>>> b/drivers/staging/brcm80211/Kconf
>>> index 6b74685..228ec37 100644
>>> --- a/drivers/staging/brcm80211/Kconfig
>>> +++ b/drivers/staging/brcm80211/Kconfig
>>> @@ -1,6 +1,6 @@
>>>   menuconfig BRCM80211
>>>          tristate "Broadcom 802.11 WLAN driver for bcm43xx chips"
>>> -       depends on PCI&&  WLAN
>>> +       depends on WLAN
>>>          select WIRELESS_EXT
>>>          select WEXT_PRIV
>>>          default N
>>> @@ -9,6 +9,6 @@ menuconfig BRCM80211
>>>
>>>   config BRCM80211_PCI
>>>          bool "Broadcom 802.11 WLAN NIC driver"
>>> -       depends on BRCM80211
>>> +       depends on BRCM80211&&  PCI&&  MAC80211
>>>          default y
>>>
>>>
>>> Our fullmac sdio driver is going to use the brcm80211 framework, and
>>> it'll only need CFG80211.
>>
>> Care to send this in a patch-format that I can apply it (i.e. proper
>> changelog entry, reported-by:, signed-off-by:, etc.)?
> 
> Yes, as soon as I figure out the full fix.  There's a build error if
> BRCM80211 is set and BRCM80211_PCI is not set (somebody pointed this out
> a couple days ago) that I'd like to resolve also.

Yes, I reported that also.  Glad to hear that it will be addressed.

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-09-21 18:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21  7:00 linux-next: Tree for September 21 Stephen Rothwell
2010-09-21 16:35 ` [PATCH -next] staging: brcm80211 depends on MAC80211 Randy Dunlap
2010-09-21 17:23   ` Henry Ptasinski
2010-09-21 17:25     ` Randy Dunlap
2010-09-21 18:06     ` Greg KH
2010-09-21 18:16       ` Henry Ptasinski
2010-09-21 18:18         ` Randy Dunlap [this message]
2010-09-21 16:53 ` linux-next: Tree for September 21 (staging/keucr) Randy Dunlap
2010-09-21 17:08   ` Greg KH

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=4C98F6DC.1070005@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=brudley@broadcom.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=henryp@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=noheek@broadcom.com \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).