From: Johannes Berg <johannes@sipsolutions.net>
To: saravanad@posedge.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211: re-organize the rx rate calculation logic
Date: Mon, 26 Nov 2012 16:08:10 +0100 [thread overview]
Message-ID: <1353942490.2800.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <d4c0566bd33c1afdcc0f7b820024d19f@posedge.com>
On Mon, 2012-11-26 at 04:17 -0800, saravanad@posedge.com wrote:
> Mac80211: currently the logic to calculate the rx rate is accessible
> only in the cfg.c as the rate_idx_to_bitrate() is static function.
> The rx rate calculation might be needed by other files(modules) of
> mac80211(possibly debugfs). So grouping the rx rate calculation logic to
> a separate function which can be accessed from other files. This change
> will make the rx rate calculation implementation similar to tx rate.
Generally, this seems fine. Your patches are line-wrapped though.
> Signed-off-by: Saravana <saravanad@posedge.com>
> ---
> The diff file is generated from wireless-testing git tree.
I just changed this code in mac80211-next and would appreciate if you
would rebase onto that.
> +void sta_set_rate_info_rx(struct sta_info *sta, struct rate_info
> *rinfo)
> +{
> + rinfo->flags = 0;
> + if (sta->last_rx_rate_flag & RX_FLAG_HT)
> + rinfo->flags |= RATE_INFO_FLAGS_MCS;
> + if (sta->last_rx_rate_flag & RX_FLAG_40MHZ)
> + rinfo->flags |= RATE_INFO_FLAGS_40_MHZ_WIDTH;
> + if (sta->last_rx_rate_flag & RX_FLAG_SHORT_GI)
> + rinfo->flags |= RATE_INFO_FLAGS_SHORT_GI;
> + rate_idx_to_bitrate(rinfo, sta, sta->last_rx_rate_idx);
> +
> +}
> static void sta_set_sinfo(struct sta_info *sta, struct station_info
> *sinfo)
That blank line is in the wrong spot, it should be after the closing
bracket :)
johannes
next prev parent reply other threads:[~2012-11-26 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 12:17 [RFC] mac80211: re-organize the rx rate calculation logic saravanad
2012-11-26 15:08 ` Johannes Berg [this message]
2012-11-27 6:20 ` Saravana
2012-11-27 7:42 ` Saravana
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=1353942490.2800.0.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=saravanad@posedge.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).