From: Rajkumar Manoharan <rmanohar@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3 0/3] wireless: Add support to probe unexercised mesh link
Date: Wed, 10 Apr 2019 17:02:04 -0700 [thread overview]
Message-ID: <8cb47c1517ab2574c19efae101d6de21@codeaurora.org> (raw)
In-Reply-To: <1ed09282bb0efb801a29d40eca7a09af077ad1d3.camel@sipsolutions.net>
On 2019-04-09 05:02, Johannes Berg wrote:
> On Wed, 2019-04-03 at 12:14 -0700, Rajkumar Manoharan wrote:
>> Consider below mesh topology.
>>
>> MP1
>> / \
>> / \
>> MP2 --- MP3
>>
>> Assume that even though MP1 & MP3 have direct mesh links, the path was
>> established via MP2. (MP1 <-> MP2 <-> MP3). The 1-hop mesh link MP1
>> <-> MP3
>> never be excercised till the current path is terminated. As of now,
>> there
>> is no option to send data frame to pick other than primary path. So
>> mesh
>> link metric between MP1 & MP3 never be updated. This series allows
>> user
>> to send data to 1-hop mesh peers through unexercised mesh path.
>>
>> -Rajkumar
>>
>> v3: Rebased the changes on TOT
>
> Hmm. Please rebase again, and retest, because I just applied this and
> it
> doesn't even compile ...
>
Sure.. will send next version on top of mac80211-next.
-Rajkumar
prev parent reply other threads:[~2019-04-11 0:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 19:14 [PATCH v3 0/3] wireless: Add support to probe unexercised mesh link Rajkumar Manoharan
2019-04-03 19:14 ` [PATCH v3 1/3] cfg80211: add " Rajkumar Manoharan
2019-04-03 19:14 ` [PATCH v3 2/3] mac80211: add option for setting control flags Rajkumar Manoharan
2019-04-03 19:14 ` [PATCH v3 3/3] mac80211: probe unexercised mesh links Rajkumar Manoharan
2019-04-09 12:02 ` [PATCH v3 0/3] wireless: Add support to probe unexercised mesh link Johannes Berg
2019-04-11 0:02 ` Rajkumar Manoharan [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=8cb47c1517ab2574c19efae101d6de21@codeaurora.org \
--to=rmanohar@codeaurora.org \
--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.