From: "John W. Linville" <linville@tuxdriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the wireless tree
Date: Wed, 23 Jun 2010 10:57:04 -0400 [thread overview]
Message-ID: <20100623145703.GD15205@tuxdriver.com> (raw)
In-Reply-To: <20100623125149.bdd7b1e6.sfr@canb.auug.org.au>
On Wed, Jun 23, 2010 at 12:51:49PM +1000, Stephen Rothwell wrote:
> Hi John,
>
> After merging the wireless tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> ERROR: "mesh_handler_def" [drivers/net/wireless/libertas/libertas.ko] undefined!
>
> Caused by commit cbca36ab906ce8c8d959eca1e0b5465e9182b0f0 ("Libertas:
> cfg80211 support") which removed mesh_handler_def even though there is
> still a reference to it in drivers/net/wireless/libertas/mesh.c when
> WIRELESS_EXT is defined.
>
> I have used the wireless tree from next-20100622 for today.
Yes, sorry about that! I'll correct it today.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-06-23 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 2:51 linux-next: build failure after merge of the wireless tree Stephen Rothwell
2010-06-23 14:57 ` John W. Linville [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-12 2:36 Stephen Rothwell
2011-06-23 3:03 Stephen Rothwell
2011-06-23 3:46 ` David Miller
2011-06-28 18:11 ` Gustavo F. Padovan
2011-05-16 2:02 Stephen Rothwell
2011-05-16 18:08 ` John W. Linville
2010-03-10 3:36 Stephen Rothwell
2010-03-10 5:53 ` Juuso Oikarinen
2010-03-10 11:19 ` Luciano Coelho
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=20100623145703.GD15205@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).