linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Mohammed Shafi Shajakhan <mshajakhan@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211: Fix parsing of MCS rates to radiotap
Date: Fri, 04 Feb 2011 16:39:02 +0100	[thread overview]
Message-ID: <1296833942.3671.12.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1296833778-2912-1-git-send-email-mshajakhan@atheros.com>

On Fri, 2011-02-04 at 21:06 +0530, Mohammed Shafi Shajakhan wrote:
> From: Mohammed Shafi Shajakhan <mshajakhan@atheros.com>
> 
> Previously the MCS rate elements were parsed at the wrong position
> 
> Signed-off-by: Mohammed Shafi Shajakhan <mshajakhan@atheros.com>
> ---
>  net/mac80211/rx.c |   31 ++++++++++---------------------
>  1 files changed, 10 insertions(+), 21 deletions(-)
> 
> diff --git a/net/mac80211/rx.c b/net/mac80211/rx.c
> index c08b8e9..27b4b1f 100644
> --- a/net/mac80211/rx.c
> +++ b/net/mac80211/rx.c
> @@ -141,14 +141,16 @@ ieee80211_add_rx_radiotap_header(struct ieee80211_local *local,
>  
>  	/* IEEE80211_RADIOTAP_RATE */
>  	if (status->flag & RX_FLAG_HT) {
> -		/*
> -		 * TODO: add following information into radiotap header once
> -		 * suitable fields are defined for it:
> -		 * - MCS index (status->rate_idx)
> -		 * - HT40 (status->flag & RX_FLAG_40MHZ)
> -		 * - short-GI (status->flag & RX_FLAG_SHORT_GI)
> -		 */
> -		*pos = 0;

Alright, so I forgot to remove this comment, but what made you think
that I added the code in the wrong place??

totally NAK, this breaks radiotap. Removing the comment there is fine,
replace it with

/*
 * MCS information is a separate field in radiotap,
 * added below.
 */

johannes


  reply	other threads:[~2011-02-04 15:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 15:36 [RFC] mac80211: Fix parsing of MCS rates to radiotap Mohammed Shafi Shajakhan
2011-02-04 15:39 ` Johannes Berg [this message]
2011-02-04 16:01   ` Mohammed Shafi

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=1296833942.3671.12.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mshajakhan@atheros.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;
as well as URLs for NNTP newsgroup(s).