From: Johannes Berg <johannes@sipsolutions.net>
To: "Stefanik Gábor" <netrolller.3d@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 2/3] mac80211: Make use of the new F_TX_NOACK and F_TX_NOSEQ Radiotap TX flags
Date: Fri, 12 Dec 2008 23:39:18 +0100 [thread overview]
Message-ID: <1229121558.3565.6.camel@johannes.berg> (raw)
In-Reply-To: <69e28c910812121432n6e84de41s94a887110051a1dd@mail.gmail.com> (sfid-20081212_233241_155436_BE5AE965)
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
On Fri, 2008-12-12 at 23:32 +0100, Stefanik Gábor wrote:
> Honor the 2 new flags in the "TX Flags" Radiotap field, introduced in
> the previous commit.
>
> Signed-off-by: Gábor Stefanik <netrolller.3d@gmail.com>
>
> ---
>
> Patch also available as an attachment in case Gmail decides to damage it.
>
> diff --git a/net/mac80211/ieee80211_i.h b/net/mac80211/ieee80211_i.h
> index 155a204..141099a 100644
> --- a/net/mac80211/ieee80211_i.h
> +++ b/net/mac80211/ieee80211_i.h
> @@ -143,6 +143,8 @@ typedef unsigned __bitwise__ ieee80211_tx_result;
> #define IEEE80211_TX_FRAGMENTED BIT(0)
> #define IEEE80211_TX_UNICAST BIT(1)
> #define IEEE80211_TX_PS_BUFFERED BIT(2)
> +#define IEEE80211_TX_MON_NO_SEQ BIT(3)
> +#define IEEE80211_TX_MON_NO_ACK BIT(4)
You don't need that, you can directly modify info.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-12-12 22:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 22:32 [RFC 2/3] mac80211: Make use of the new F_TX_NOACK and F_TX_NOSEQ Radiotap TX flags Stefanik Gábor
2008-12-12 22:39 ` Johannes Berg [this message]
2008-12-12 22:43 ` Stefanik Gábor
2008-12-12 22:45 ` Johannes Berg
2008-12-12 22:51 ` Stefanik Gábor
2008-12-12 22:52 ` Johannes Berg
2008-12-12 23:00 ` Stefanik Gábor
2008-12-12 23:01 ` Johannes Berg
2008-12-12 22:56 ` 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=1229121558.3565.6.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netrolller.3d@gmail.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