linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Greg KH <greg@kroah.com>,
	driverdevel <devel@driverdev.osuosl.org>,
	linux-next@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	Joe Perches <joe@perches.com>, Naveen Singh <nsingh@atheros.com>
Subject: Re: staging: fix ath6kl build when CFG80211 is not enabled
Date: Tue, 28 Jun 2011 14:21:48 -0700	[thread overview]
Message-ID: <20110628212148.GA27939@suse.de> (raw)
In-Reply-To: <4E0A3BC8.6000504@oracle.com>

On Tue, Jun 28, 2011 at 01:38:32PM -0700, Randy Dunlap wrote:
> On 06/28/11 13:06, Greg KH wrote:
> > On Fri, May 27, 2011 at 01:03:21PM -0700, Randy Dunlap wrote:
> >>
> >> From: Randy Dunlap <randy.dunlap@oracle.com>
> >>
> >> Fix build errors when CONFIG_CFG80211 is not enabled:
> >>
> >> drivers/built-in.o: In function `ar6k_cfg80211_deinit':
> >> (.text+0x189b71): undefined reference to `cfg80211_scan_done'
> >> drivers/built-in.o: In function `ar6k_cfg80211_deinit':
> >> (.text+0x189b86): undefined reference to `wiphy_unregister'
> >> drivers/built-in.o: In function `ar6k_cfg80211_deinit':
> >> (.text+0x189b8d): undefined reference to `wiphy_free'
> >> drivers/built-in.o: In function `ar6k_cfg80211_init':
> >> (.text+0x18add7): undefined reference to `wiphy_new'
> >> drivers/built-in.o: In function `ar6k_cfg80211_init':
> >> (.text+0x18ae48): undefined reference to `wiphy_register'
> >> drivers/built-in.o: In function `ar6k_cfg80211_tkip_micerr_event':
> >> (.text+0x18ae95): undefined reference to `cfg80211_michael_mic_failure'
> >> drivers/built-in.o: In function `ar6k_cfg80211_scan_node':
> >> (.text+0x18afb5): undefined reference to `__ieee80211_get_channel'
> >> drivers/built-in.o: In function `ar6k_cfg80211_scan_node':
> >> (.text+0x18afd2): undefined reference to `cfg80211_inform_bss_frame'
> >> drivers/built-in.o: In function `ar6k_cfg80211_disconnect_event':
> >> (.text+0x18b046): undefined reference to `cfg80211_ibss_joined'
> >> drivers/built-in.o: In function `ar6k_cfg80211_disconnect_event':
> >> (.text+0x18b176): undefined reference to `cfg80211_connect_result'
> >> drivers/built-in.o: In function `ar6k_cfg80211_disconnect_event':
> >> (.text+0x18b190): undefined reference to `cfg80211_disconnected'
> >> drivers/built-in.o: In function `ar6k_cfg80211_connect_event':
> >> (.text+0x18b291): undefined reference to `cfg80211_get_bss'
> >> drivers/built-in.o: In function `ar6k_cfg80211_connect_event':
> >> (.text+0x18b457): undefined reference to `cfg80211_put_bss'
> >> drivers/built-in.o: In function `ar6k_cfg80211_connect_event':
> >> (.text+0x18b4fa): undefined reference to `cfg80211_roamed'
> >>
> >> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> >> Cc: Luis R. Rodriguez <mcgrof@gmail.com>
> >> Cc: Joe Perches <joe@perches.com>
> >> Cc: Naveen Singh <nsingh@atheros.com>
> >> ---
> >>  drivers/staging/ath6kl/Kconfig |    1 +
> >>  1 file changed, 1 insertion(+)
> >>
> >> --- linux-next-20110517.orig/drivers/staging/ath6kl/Kconfig
> >> +++ linux-next-20110517/drivers/staging/ath6kl/Kconfig
> >> @@ -1,6 +1,7 @@
> >>  config ATH6K_LEGACY
> >>  	tristate "Atheros AR6003 support (non mac80211)"
> >>          depends on MMC && WLAN
> >> +	depends on CFG80211
> > 
> > Is this still needed in the next linux-next release?
> 
> It's already there, isn't it?
> 
> config ATH6K_LEGACY
> 	tristate "Atheros AR6003 support (non mac80211)"
>         depends on MMC && WLAN
> 	depends on CFG80211
>         select WIRELESS_EXT
>         select WEXT_PRIV

I thought so, hence my confusion :)

      reply	other threads:[~2011-06-28 21:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27 20:03 [PATCH -next] staging: fix ath6kl build when CFG80211 is not enabled Randy Dunlap
2011-06-28 20:06 ` Greg KH
2011-06-28 20:38   ` Randy Dunlap
2011-06-28 21:21     ` Greg KH [this message]

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=20110628212148.GA27939@suse.de \
    --to=gregkh@suse.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=nsingh@atheros.com \
    --cc=randy.dunlap@oracle.com \
    /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).