From: Antonio Quartulli <antonio@open-mesh.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iw: print expected throughput when dumping station
Date: Sun, 18 May 2014 06:13:09 +0200 [thread overview]
Message-ID: <53783355.6070205@open-mesh.com> (raw)
In-Reply-To: <1400350632-2422-1-git-send-email-antonio@meshcoding.com>
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
On 17/05/14 20:17, Antonio Quartulli wrote:
> From: Antonio Quartulli <antonio@open-mesh.com>
>
> Signed-off-by: Antonio Quartulli <antonio@open-mesh.com>
> ---
>
> This patch is based on the "Export the expected throughput towards a peer"
> patchset sent on linux-wireless
well, this just means that the iw private copy of nl80211.h needs to be
updated in order to use this feature.
Cheers,
--
--
Antonio Quartulli
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-05-18 4:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 18:17 [PATCH] iw: print expected throughput when dumping station Antonio Quartulli
2014-05-18 4:13 ` Antonio Quartulli [this message]
2014-06-03 19:47 ` Johannes Berg
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=53783355.6070205@open-mesh.com \
--to=antonio@open-mesh.com \
--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 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).