From: Antonio Quartulli <antonio@open-mesh.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: devel@lists.open80211s.org, b.a.t.m.a.n@lists.open-mesh.org,
linux-wireless@vger.kernel.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv3 2/4] cfg80211: export expected throughput via nl80211 (GET_STATION)
Date: Mon, 19 May 2014 17:49:27 +0200 [thread overview]
Message-ID: <537A2807.1070703@open-mesh.com> (raw)
In-Reply-To: <1400511606.4273.18.camel@jlt4.sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
On 19/05/14 17:00, Johannes Berg wrote:
> On Sat, 2014-05-17 at 18:41 +0200, Antonio Quartulli wrote:
>> From: Antonio Quartulli <antonio@open-mesh.com>
>>
>> Send the expected throughput when replying to a GET_STATION
>> command via nl80211.
>
> Since both are pretty short I think you might also just squash patches 1
> and 2.
Ok, will resend with 1/4 and 2/4 squashed and I'll add the u32 spec.
Thanks!
--
Antonio Quartulli
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Antonio Quartulli <antonio@open-mesh.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: b.a.t.m.a.n@lists.open-mesh.org, devel@lists.open80211s.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCHv3 2/4] cfg80211: export expected throughput via nl80211 (GET_STATION)
Date: Mon, 19 May 2014 17:49:27 +0200 [thread overview]
Message-ID: <537A2807.1070703@open-mesh.com> (raw)
In-Reply-To: <1400511606.4273.18.camel@jlt4.sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
On 19/05/14 17:00, Johannes Berg wrote:
> On Sat, 2014-05-17 at 18:41 +0200, Antonio Quartulli wrote:
>> From: Antonio Quartulli <antonio@open-mesh.com>
>>
>> Send the expected throughput when replying to a GET_STATION
>> command via nl80211.
>
> Since both are pretty short I think you might also just squash patches 1
> and 2.
Ok, will resend with 1/4 and 2/4 squashed and I'll add the u32 spec.
Thanks!
--
Antonio Quartulli
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-05-19 15:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 16:41 [B.A.T.M.A.N.] [PATCHv3 0/6] Export the expected throughput towards a peer Antonio Quartulli
2014-05-17 16:41 ` Antonio Quartulli
2014-05-17 16:41 ` [B.A.T.M.A.N.] [PATCHv3 1/4] cfg80211: export expected throughput through get_station() Antonio Quartulli
2014-05-17 16:41 ` Antonio Quartulli
2014-05-17 16:41 ` [B.A.T.M.A.N.] [PATCHv3 2/4] cfg80211: export expected throughput via nl80211 (GET_STATION) Antonio Quartulli
2014-05-17 16:41 ` Antonio Quartulli
2014-05-19 14:59 ` [B.A.T.M.A.N.] " Johannes Berg
2014-05-19 14:59 ` Johannes Berg
2014-05-19 15:00 ` [B.A.T.M.A.N.] " Johannes Berg
2014-05-19 15:00 ` Johannes Berg
2014-05-19 15:49 ` Antonio Quartulli [this message]
2014-05-19 15:49 ` Antonio Quartulli
2014-05-17 16:41 ` [B.A.T.M.A.N.] [PATCHv3 3/4] mac80211: export the expected throughput Antonio Quartulli
2014-05-17 16:41 ` Antonio Quartulli
2014-05-17 16:41 ` [B.A.T.M.A.N.] [PATCHv3 4/4] cfg80211: implement cfg80211_get_station cfg80211 API Antonio Quartulli
2014-05-17 16:41 ` Antonio Quartulli
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=537A2807.1070703@open-mesh.com \
--to=antonio@open-mesh.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=devel@lists.open80211s.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.