From: Larry Finger <Larry.Finger@lwfinger.net>
To: Bruno Randolf <br1@einfach.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
linville@tuxdriver.com, Johannes Berg <johannes@sipsolutions.net>
Subject: Re: build error without CONFIG_MAC80211_MESH
Date: Mon, 06 Dec 2010 20:36:06 -0600 [thread overview]
Message-ID: <4CFD9D96.6090003@lwfinger.net> (raw)
In-Reply-To: <201012071123.03046.br1@einfach.org>
On 12/06/2010 08:23 PM, Bruno Randolf wrote:
> Hi!
>
> Building current wireless-testing (master-2010-12-06) without the Mesh option
> is broken:
>
> CC [M] net/mac80211/main.o
> /home/br1/ath/wireless-testing/net/mac80211/main.c: In function
> ‘ieee80211_bss_info_change_notify’:
> /home/br1/ath/wireless-testing/net/mac80211/main.c:250: error: ‘union
> <anonymous>’ has no member named ‘mesh’
> make[3]: *** [net/mac80211/main.o] Error 1
> make[2]: *** [net/mac80211] Error 2
> make[1]: *** [net] Error 2
> make: *** [sub-make] Error 2
>
> It needs something like:
>
> diff --git a/net/mac80211/main.c b/net/mac80211/main.c
> index 40bd12e..3d988ca 100644
> --- a/net/mac80211/main.c
> +++ b/net/mac80211/main.c
> @@ -245,10 +245,12 @@ void ieee80211_bss_info_change_notify(struct
> ieee80211_sub_if_data *sdata,
> sdata->vif.bss_conf.enable_beacon =
> !!sdata->u.ibss.presp;
> break;
> +#ifdef CONFIG_MAC80211_MESH
> case NL80211_IFTYPE_MESH_POINT:
> sdata->vif.bss_conf.enable_beacon =
> !!sdata->u.mesh.mesh_id_len;
> break;
> +#endif
> default:
> /* not reached */
> WARN_ON(1);
Happens here too.
Larry
next prev parent reply other threads:[~2010-12-07 2:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 2:23 build error without CONFIG_MAC80211_MESH Bruno Randolf
2010-12-07 2:36 ` Larry Finger [this message]
2010-12-07 10:05 ` 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=4CFD9D96.6090003@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=br1@einfach.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).