public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: Accept only filled wifi station info
Date: Fri, 09 Jun 2017 16:06:43 +0200	[thread overview]
Message-ID: <1548734.CEMtPVhoG8@sven-edge> (raw)
In-Reply-To: <20170609130255.8577-2-sven@narfation.org>

[-- Attachment #1: Type: text/plain, Size: 863 bytes --]

On Freitag, 9. Juni 2017 15:02:55 CEST Sven Eckelmann wrote:
[...]
>  #if LINUX_VERSION_CODE < KERNEL_VERSION(4, 8, 0)
> diff --git a/net/batman-adv/bat_v_elp.c b/net/batman-adv/bat_v_elp.c
> index 96e73337..16552568 100644
> --- a/net/batman-adv/bat_v_elp.c
> +++ b/net/batman-adv/bat_v_elp.c
> @@ -111,6 +111,8 @@ static u32 batadv_v_elp_get_throughput(struct batadv_hardif_neigh_node *neigh)
>  		}
>  		if (ret)
>  			goto default_throughput;
> +		if (!(sinfo.filled & STATION_INFO_EXPECTED_THROUGHPUT))
> +			goto default_throughput;
>  
>  		return sinfo.expected_throughput / 100;
>  	}
> 

Looks like STATION_INFO_EXPECTED_THROUGHPUT was removed in 
319090bf6c75e3ad42a8c74973be5e78ae4f948f and 
BIT(NL80211_STA_INFO_EXPECTED_THROUGHPUT) must now be used. Of course, 
NL80211_STA_INFO_EXPECTED_THROUGHPUT doesn't have the value 28 :(

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-06-09 14:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-09 13:02 [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: Use default throughput value on cfg80211 error Sven Eckelmann
2017-06-09 13:02 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: Accept only filled wifi station info Sven Eckelmann
2017-06-09 14:06   ` Sven Eckelmann [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=1548734.CEMtPVhoG8@sven-edge \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.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