From: "John W. Linville" <linville@tuxdriver.com>
To: Brian Haley <brian.haley@hp.com>
Cc: johannes@sipsolutions.net,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Can't build net-next-2.6 without CONFIG_MAC80211_MESH
Date: Tue, 30 Sep 2008 10:43:22 -0400 [thread overview]
Message-ID: <20080930144322.GC3386@tuxdriver.com> (raw)
In-Reply-To: <48E2394A.3010707@hp.com>
On Tue, Sep 30, 2008 at 10:35:54AM -0400, Brian Haley wrote:
> Sorry if this has been discussed/fixed already, but I just noticed last
> night I couldn't build net-next-2.6:
>
> Kernel: arch/x86/boot/bzImage is ready (#71)
> ERROR: "mpp_path_lookup" [net/mac80211/mac80211.ko] undefined!
> ERROR: "mpp_path_add" [net/mac80211/mac80211.ko] undefined!
>
> These are defined in net/mac80211/mesh_pathtbl.c, but being called from
> rx.c and tx.c, but I'm not building the mesh files:
>
> --> grep CONFIG_MAC80211 .config
> CONFIG_MAC80211=m
> CONFIG_MAC80211_RC_PID=y
> CONFIG_MAC80211_RC_DEFAULT_PID=y
> CONFIG_MAC80211_RC_DEFAULT="pid"
> # CONFIG_MAC80211_MESH is not set
> # CONFIG_MAC80211_LEDS is not set
> # CONFIG_MAC80211_DEBUGFS is not set
> # CONFIG_MAC80211_DEBUG_MENU is not set
>
> make oldconfig didn't make any changes, so I think the config is valid.
I have the fix queued in wireless-testing -- I think/thought Dave
is/was traveling, so I didn't rush to push it to net-next-2.6.
I'll get that pull request assembled today. In the meantime, just
enable CONFIG_MAC80211_MESH.
Thanks,
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
prev parent reply other threads:[~2008-09-30 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 14:35 Can't build net-next-2.6 without CONFIG_MAC80211_MESH Brian Haley
2008-09-30 14:43 ` John W. Linville [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=20080930144322.GC3386@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=brian.haley@hp.com \
--cc=johannes@sipsolutions.net \
--cc=netdev@vger.kernel.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.