From: Johannes Berg <johannes@sipsolutions.net>
To: "Altshul, Maxim" <maxim.altshul@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "john.stultz@linaro.org" <john.stultz@linaro.org>,
Kalle Valo <kvalo@codeaurora.org>,
Eliad Peller <eliad@wizery.com>,
"Machani, Yaniv" <yanivma@ti.com>
Subject: Re: [PATCH 1/2] mac80211/wlcore: Add ieee80211_hw variable to get_expected_throughput
Date: Tue, 09 Aug 2016 09:58:30 +0200 [thread overview]
Message-ID: <1470729510.28531.13.camel@sipsolutions.net> (raw)
In-Reply-To: <F52F6CF13382174692D81838F3DBEF41136F07B6@DFRE01.ent.ti.com>
On Mon, 2016-08-08 at 10:42 +0000, Altshul, Maxim wrote:
> Yes, exactly! Should I send the patch then so that we protect
> get_expected_throughput?
Yes please.
> If so, then please have a look at my previous mesh patch (not yet
> applied) "[PATCH v3] mac80211: mesh: Add support for HW RC
> implementation".
Looks ok, I just haven't applied it because net-next was closed until
today :)
> If you approve the mesh patch, then I will send two patches:
> 1. Check for sta->uploaded in the drv wrapper (will change the drv
> wrapper header to get sta_info)
> 2. v4 for the mesh patch with respect to header change in patch 1.
I don't think adding the check changes anything wrt. the mesh patch?
johannes
next prev parent reply other threads:[~2016-08-09 7:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 12:43 [PATCH 0/2] get_expected_throughput interface update Maxim Altshul
2016-08-04 12:43 ` [PATCH 1/2] mac80211/wlcore: Add ieee80211_hw variable to get_expected_throughput Maxim Altshul
2016-08-04 12:43 ` [PATCH 2/2] wlcore: Remove wl pointer from wl_sta structure Maxim Altshul
2016-08-04 21:31 ` John Stultz
2016-08-15 7:56 ` Kalle Valo
2016-08-15 7:56 ` Kalle Valo
2016-08-04 21:31 ` [PATCH 1/2] mac80211/wlcore: Add ieee80211_hw variable to get_expected_throughput John Stultz
2016-08-05 5:40 ` Johannes Berg
2016-08-05 6:03 ` John Stultz
2016-08-05 12:22 ` Johannes Berg
2016-08-05 12:24 ` Johannes Berg
2016-08-05 13:25 ` Altshul, Maxim
2016-08-05 15:34 ` Johannes Berg
2016-08-07 13:42 ` Altshul, Maxim
2016-08-08 6:10 ` Johannes Berg
2016-08-08 10:42 ` Altshul, Maxim
2016-08-09 7:58 ` Johannes Berg [this message]
2016-08-10 8:03 ` Altshul, Maxim
2016-08-15 7:59 ` Kalle Valo
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=1470729510.28531.13.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=eliad@wizery.com \
--cc=john.stultz@linaro.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxim.altshul@ti.com \
--cc=yanivma@ti.com \
/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.