From: Johannes Berg <johannes@sipsolutions.net>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: Sujith Manoharan <sujith@msujith.org>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 3/4] ath10k: Fix no-ack frame status
Date: Fri, 12 Dec 2014 12:40:44 +0100 [thread overview]
Message-ID: <1418384444.2470.22.camel@sipsolutions.net> (raw)
In-Reply-To: <87oarazecg.fsf@kamboji.qca.qualcomm.com>
On Thu, 2014-12-11 at 12:10 +0200, Kalle Valo wrote:
> Sujith Manoharan <sujith@msujith.org> writes:
>
> > From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
> >
> > Use the new IEEE80211_TX_STAT_NOACK_TRANSMITTED flag
> > to indicate successful transmission of no-ack frames.
> > This fixes multicast frame accounting.
> >
> > Cc: ath10k@lists.infradead.org
> > Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
>
> Johannes, are you planning to take this? Or should I take this once the
> corresponding mac80211 patch trickles down to my tree?
I don't really want to take the driver patches, but I'll try to get to
the mac80211 ones today.
johannes
next prev parent reply other threads:[~2014-12-12 11:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 15:56 [PATCH 1/4] mac80211: Move IEEE80211_TX_CTL_PS_RESPONSE Sujith Manoharan
2014-12-10 15:56 ` [PATCH 2/4] mac80211: Fix accounting of multicast frames Sujith Manoharan
2014-12-12 12:48 ` Johannes Berg
2014-12-15 1:41 ` Sujith Manoharan
2014-12-10 15:56 ` [PATCH 3/4] ath10k: Fix no-ack frame status Sujith Manoharan
2014-12-11 10:10 ` Kalle Valo
2014-12-12 11:40 ` Johannes Berg [this message]
2014-12-15 1:39 ` Sujith Manoharan
2014-12-15 8:27 ` Kalle Valo
2015-03-30 13:41 ` Kalle Valo
2015-04-03 1:12 ` Sujith Manoharan
2015-04-09 12:11 ` Kalle Valo
2014-12-10 15:56 ` [PATCH 4/4] ath9k: " Sujith Manoharan
2014-12-12 12:45 ` [PATCH 1/4] mac80211: Move IEEE80211_TX_CTL_PS_RESPONSE 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=1418384444.2470.22.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sujith@msujith.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).