From: Dan Williams <dcbw@redhat.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-wireless@vger.kernel.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
libertas-dev@lists.infradead.org,
Holger Schurig <hs4233@mail.mn-solutions.de>
Subject: Re: linux-next: Tree for October 7 (libertas build failure)
Date: Wed, 07 Oct 2009 11:12:00 -0700 [thread overview]
Message-ID: <1254939120.16001.45.camel@localhost.localdomain> (raw)
In-Reply-To: <20091007105210.409a1991.randy.dunlap@oracle.com>
On Wed, 2009-10-07 at 10:52 -0700, Randy Dunlap wrote:
> On Wed, 7 Oct 2009 17:35:17 +1100 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20091006:
>
>
> drivers/built-in.o: In function `lbs_cfg_free':
> (.text+0x3479e0): undefined reference to `wiphy_unregister'
> drivers/built-in.o: In function `lbs_cfg_free':
> (.text+0x3479e7): undefined reference to `wiphy_free'
> drivers/built-in.o: In function `lbs_cfg_register':
> (.text+0x347a52): undefined reference to `wiphy_register'
> drivers/built-in.o: In function `lbs_cfg_alloc':
> (.text+0x347acf): undefined reference to `wiphy_new'
Holger, perhaps we need some Kconfig updates to select cfg80211?
Dan
next prev parent reply other threads:[~2009-10-07 18:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091007173517.abfcfa2a.sfr@canb.auug.org.au>
2009-10-07 17:52 ` linux-next: Tree for October 7 (libertas build failure) Randy Dunlap
2009-10-07 18:12 ` Dan Williams [this message]
2009-10-07 22:34 ` Johannes Berg
2009-10-07 17:57 ` linux-next: Tree for October 7 (wireless/wext) Randy Dunlap
2009-10-07 21:07 ` [PATCH] wireless: make WEXT_SPY and WEXT_PRIV select WEXT_CORE John W. Linville
2009-10-07 21:55 ` Randy Dunlap
2009-10-07 22:34 ` Johannes Berg
2009-10-07 22:54 ` Randy Dunlap
2009-10-07 23:14 ` Johannes Berg
2009-10-08 0:12 ` Randy Dunlap
2009-10-08 9:48 ` Johannes Berg
2009-10-08 15:06 ` Randy Dunlap
2009-10-08 18:29 ` Johannes Berg
2009-10-09 16:06 ` Randy Dunlap
2009-10-09 16:14 ` Johannes Berg
2009-10-09 16:32 ` 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=1254939120.16001.45.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=randy.dunlap@oracle.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).