From: Johannes Berg <johannes@sipsolutions.net>
To: agreen@cococorp.com
Cc: linux-wireless@vger.kernel.org, Jesse Jones <jjones@cococorp.com>
Subject: Re: [PATCH] mac80211: Fix incorrectly named last_hop_metric variable in mesh_rx_path_sel_frame
Date: Tue, 09 Jun 2015 21:53:59 +0200 [thread overview]
Message-ID: <1433879639.1892.20.camel@sipsolutions.net> (raw)
In-Reply-To: <5571FBFA.9060902@cococorp.com> (sfid-20150605_214446_863932_9DD1F8E8)
On Fri, 2015-06-05 at 12:43 -0700, Alexis Green wrote:
> The last hop metric should refer to link cost (this is how
> hwmp_route_info_get uses it for example). But in mesh_rx_path_sel_frame
> we are not dealing with link cost but with the total cost to the origin
> of a PREQ or PREP.
>
> Signed-off-by: Alexis Green <agreen@cococorp.com>
> CC: Jesse Jones <jjones@cococorp.com>
Applied. This one worked, but the other ones you sent didn't.
johannes
prev parent reply other threads:[~2015-06-09 19:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 19:43 [PATCH] mac80211: Fix incorrectly named last_hop_metric variable in mesh_rx_path_sel_frame Alexis Green
2015-06-09 19:53 ` 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=1433879639.1892.20.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=agreen@cococorp.com \
--cc=jjones@cococorp.com \
--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 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).