From: "John W. Linville" <linville@tuxdriver.com>
To: Davide Pesavento <davidepesa@gmail.com>
Cc: linux-wireless@vger.kernel.org, johannes@sipsolutions.net,
YanBo <dreamfly281@gmail.com>
Subject: Re: wireless-testing modpost failure
Date: Fri, 26 Sep 2008 15:00:07 -0400 [thread overview]
Message-ID: <20080926190007.GD3483@tuxdriver.com> (raw)
In-Reply-To: <2da21fe50809261104m3b7d99e3g8b56416b8182ca45@mail.gmail.com>
On Fri, Sep 26, 2008 at 08:04:18PM +0200, Davide Pesavento wrote:
> Hi!
>
> I just pulled from wireless-testing git tree and I'm now hitting this
> build error:
>
> Building modules, stage 2.
> MODPOST 216 modules
> ERROR: "mpp_path_lookup" [net/mac80211/mac80211.ko] undefined!
> ERROR: "mpp_path_add" [net/mac80211/mac80211.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
>
> My kernel config:
>
> $ 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
Turn this on to make it build again.
I'm not sure what the best long-term solution is. Should we define
empty versions of those functions when that config option is unset?
Or just make the whole block subject to that config option?
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
next prev parent reply other threads:[~2008-09-26 19:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 18:04 wireless-testing modpost failure Davide Pesavento
2008-09-26 19:00 ` John W. Linville [this message]
2008-09-26 19:30 ` Johannes Berg
2008-09-26 20:25 ` Davide Pesavento
2008-09-27 8:38 ` Johannes Berg
2008-09-27 9:20 ` Johannes Berg
2008-09-27 10:54 ` Davide Pesavento
2008-09-27 11:48 ` Johannes Berg
2008-09-27 12:34 ` Davide Pesavento
2008-09-27 13:16 ` Johannes Berg
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=20080926190007.GD3483@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davidepesa@gmail.com \
--cc=dreamfly281@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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.