From: Johannes Berg <johannes@sipsolutions.net>
To: Javier Cardona <javier@cozybit.com>
Cc: linux-wireless@vger.kernel.org,
Steve Derosier <steve@cozybit.com>,
devel@lists.open80211s.org
Subject: Re: [RFC 5/5 v2] cfg80211/mac80211: add mesh join/leave commands
Date: Fri, 03 Dec 2010 09:13:35 +0100 [thread overview]
Message-ID: <1291364015.3499.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTi=o08ZBhF6KmYZ-jvAzM7WoMEZztNz+0Fc+WQQi@mail.gmail.com>
On Thu, 2010-12-02 at 15:08 -0800, Javier Cardona wrote:
> Not really. Maybe this as PATCH 1/5 v3?
Sure, looks good.
> @@ -1585,6 +1588,7 @@ enum nl80211_meshconf_params {
> NL80211_MESHCONF_MAX_PEER_LINKS,
> NL80211_MESHCONF_MAX_RETRIES,
> NL80211_MESHCONF_TTL,
> + NL80211_MESHCONF_ELEMENT_TTL,
> NL80211_MESHCONF_AUTO_OPEN_PLINKS,
> NL80211_MESHCONF_HWMP_MAX_PREQ_RETRIES,
> NL80211_MESHCONF_PATH_REFRESH_TIME,
except for this bit of course, it breaks ABI. I've fixed it up.
johannes
prev parent reply other threads:[~2010-12-03 8:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 20:59 [RFC 0/5] mesh join/leave API Johannes Berg
2010-12-01 20:59 ` [RFC 1/5] mac80211: use configured mesh TTL Johannes Berg
2010-12-01 20:59 ` [RFC 2/5] mac80211: move mesh filter adjusting Johannes Berg
2010-12-01 20:59 ` [RFC 3/5] cfg80211: require add_virtual_intf to return new dev Johannes Berg
2010-12-01 20:59 ` [RFC 4/5] nl80211: refactor mesh parameter parsing Johannes Berg
2010-12-02 8:34 ` [RFC 4/5 v2] " Johannes Berg
2010-12-01 20:59 ` [RFC 5/5] cfg80211/mac80211: add mesh join/leave commands Johannes Berg
2010-12-01 21:15 ` Johannes Berg
2010-12-02 0:23 ` Javier Cardona
2010-12-02 6:57 ` Johannes Berg
2010-12-02 8:45 ` [RFC 5/5 v2] " Johannes Berg
2010-12-02 20:09 ` Javier Cardona
2010-12-02 20:14 ` Johannes Berg
2010-12-02 21:24 ` Javier Cardona
2010-12-02 21:38 ` Johannes Berg
2010-12-02 23:08 ` Javier Cardona
2010-12-03 8:13 ` Johannes Berg [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=1291364015.3499.1.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=devel@lists.open80211s.org \
--cc=javier@cozybit.com \
--cc=linux-wireless@vger.kernel.org \
--cc=steve@cozybit.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).