From: Luis Carlos Cobo <luisca@cozybit.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 07/13] o11s: support for mesh interfaces in mac80211 data path
Date: Fri, 08 Feb 2008 16:36:47 -0800 [thread overview]
Message-ID: <1202517407.7025.32.camel@localhost> (raw)
In-Reply-To: <1202345620.9965.80.camel@johannes.berg>
On Thu, 2008-02-07 at 01:53 +0100, Johannes Berg wrote:
> > + if (!is_estab_plink(hdr->addr2, rx->dev)) {
>
> This would get to be something like
>
> if (sta->flags & STA_FLAG_MESH_LINK_ESTABLISHED)
>
> right?
I probably can use just the AUTHORIZED flag.
> I suppose you should be adding sta_info structs for each mesh peer and
> set the AUTHORIZED flag on them. Is this what you were referring to in
> the patch description?
Right, and adding a pointer to a reduced mesh peer link structure with
variables only needed for mesh (it would only be allocated for mesh
interfaces).
> type == ETH_P_PAE &&
> > + if (sdata->vif.type != IEEE80211_IF_TYPE_MESH_POINT &&
> > + (!is_multicast_ether_addr(hdr.addr1) &&
> > + !(sta_flags & WLAN_STA_AUTHORIZED) &&
> > + !(ethertype == ETH_P_PAE &&
> > compare_ether_addr(dev->dev_addr,
> > skb->data + ETH_ALEN) == 0))) {
>
> That's also an artifact of not adding sta info structs, right?
Indeed, will be gone in the next round.
Btw, I will also fix all the issues I'm not commenting on in this patch
and the others. Thanks for you patience with me!
--
Luis Carlos Cobo Rus GnuPG ID: 44019B60
cozybit Inc.
next prev parent reply other threads:[~2008-02-09 0:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 19:17 [PATCH 07/13] o11s: support for mesh interfaces in mac80211 data path Luis Carlos Cobo
2008-02-07 0:53 ` Johannes Berg
2008-02-09 0:36 ` Luis Carlos Cobo [this message]
2008-02-11 9:30 ` Johannes Berg
2008-02-09 2:18 ` Luis Carlos Cobo
2008-02-11 7:50 ` 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=1202517407.7025.32.camel@localhost \
--to=luisca@cozybit.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.