From: Bob Copeland <me@bobcopeland.com>
To: Felix Fietkau <nbd@nbd.name>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, fred.veldini@gmail.com
Subject: Re: [PATCH] mac80211: mesh: flush mesh paths early in sta destroy
Date: Sat, 14 May 2016 20:07:07 -0400 [thread overview]
Message-ID: <20160515000707.GA29555@localhost> (raw)
In-Reply-To: <f898e5e4-e27a-ff5e-6deb-ed109f6ce168@nbd.name>
On Sat, May 14, 2016 at 08:54:13PM +0200, Felix Fietkau wrote:
> > + WLAN_STA_BLOCK_MPATH,
> I think this flag needs to be added to sta_flag_names in debugfs_sta.c
>
> - Felix
Good point. I also missed the part where mesh_path_assign_nexthop
should return an error to indicate the path shouldn't be activated.
So, I'll send a v2 tomorrow, additional comments welcome in the
meantime.
--
Bob Copeland %% http://bobcopeland.com/
next prev parent reply other threads:[~2016-05-15 0:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 17:49 [PATCH] mac80211: mesh: flush mesh paths early in sta destroy Bob Copeland
2016-05-14 18:54 ` Felix Fietkau
2016-05-15 0:07 ` Bob Copeland [this message]
2016-05-15 12:23 ` Bob Copeland
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=20160515000707.GA29555@localhost \
--to=me@bobcopeland.com \
--cc=fred.veldini@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
/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).