From: Luis Carlos Cobo <luisca@cozybit.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org,
Stefano Brivio <stefano.brivio@polimi.it>
Subject: Re: [PATCH 00/13 v2] o11s: mesh interface support for mac80211
Date: Mon, 25 Feb 2008 11:45:45 -0800 [thread overview]
Message-ID: <1203968745.6929.30.camel@localhost> (raw)
In-Reply-To: <1203693709.7082.35.camel@johannes.berg>
On Fri, 2008-02-22 at 16:21 +0100, Johannes Berg wrote:
> > - We no longer use directly rtnetlink for mesh peer link and mesh paths
> > operation, and use nl80211 instead.
>
> Nice too. What does libertas currently do btw?
>
iwpriv...
> > I would like to point out that it looks like we can get duplicate sta_entries,
> > or more entries than the maximum allowed, if stas are added at the same time
> > through normal network behavior and manual operation through nl80211. Please
> > correct me if I am wrong or if it is just that no interface type is supposed to
> > allow both kinds of additions.
>
> I think I CC'ed you on the patch fixing that, no?
Not sure which patch are you talking about, anyway I will check that
along with the mesh + sta_info changes testing.
--
Luis Carlos Cobo Rus GnuPG ID: 44019B60
cozybit Inc.
next prev parent reply other threads:[~2008-02-25 19:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 4:05 [PATCH 00/13 v2] o11s: mesh interface support for mac80211 Luis Carlos Cobo
2008-02-22 15:21 ` Johannes Berg
2008-02-22 15:59 ` John W. Linville
2008-02-22 16:34 ` Johannes Berg
2008-02-23 10:58 ` Johannes Berg
2008-02-25 19:47 ` Luis Carlos Cobo
2008-02-25 19:45 ` Luis Carlos Cobo [this message]
2008-02-25 19:50 ` Johannes Berg
2008-02-26 1:03 ` David Woodhouse
2008-02-26 8:22 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2008-02-22 4:05 Luis Carlos Cobo
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=1203968745.6929.30.camel@localhost \
--to=luisca@cozybit.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=stefano.brivio@polimi.it \
/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.