From: Johannes Berg <johannes@sipsolutions.net>
To: Gertjan van Wingerde <gertjan@vanwingerde.net>
Cc: Gertjan van Wingerde <gwingerde@gmail.com>,
John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: request TX status where needed
Date: Thu, 19 Nov 2009 23:33:08 +0100 [thread overview]
Message-ID: <1258669988.7094.30.camel@johannes.local> (raw)
In-Reply-To: <4B05C70D.1030703@vanwingerde.net>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
On Thu, 2009-11-19 at 23:30 +0100, Gertjan van Wingerde wrote:
> >> - if (tx_info->flags & IEEE80211_TX_CTL_REQ_TX_STATUS)
> >> + if (!(skbdesc_flags & SKBDESC_NOT_MAC80211))
> >> ieee80211_tx_status_irqsafe(rt2x00dev->hw, entry->skb);
> >> else
> >> dev_kfree_skb_irq(entry->skb);
> >
> > I'm slightly confused here. Shouldn't both the tx_info->flags and skbdesc_flags be checked here?
> > Now we run in the situation where tx_status is report even if mac80211 didn't ask for it.
> >
>
> Never mind. I missed the change from "requested" to "required" for the
> IEEE80211_TX_CTL_REQ_TX_STATUS flag.
In fact, it wouldn't matter if you gave it a TX status for the RTS or
CTS frame either, but it might be somewhat confusing :)
The "required" is also not really correct. The frame could always be
dropped elsewhere due to memory pressure or whatever... I'll need to
reword that and explain much more.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2009-11-19 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 0:08 [PATCH] mac80211: request TX status where needed Johannes Berg
2009-11-19 22:09 ` Gertjan van Wingerde
2009-11-19 22:30 ` Gertjan van Wingerde
2009-11-19 22:33 ` Johannes Berg [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=1258669988.7094.30.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=gertjan@vanwingerde.net \
--cc=gwingerde@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox