From: Johannes Berg <johannes@sipsolutions.net>
To: Mahesh Palivela <maheshp@posedge.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/3] mac80211: support VHT association
Date: Tue, 27 Nov 2012 13:44:30 +0100 [thread overview]
Message-ID: <1354020270.9576.8.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <50B4AE29.3040600@posedge.com>
On Tue, 2012-11-27 at 17:42 +0530, Mahesh Palivela wrote:
> > + vht_cap = (void *)(vht_cap_ie + 2);
> > + tx_mcs_map = le16_to_cpu(vht_cap->supp_mcs.tx_mcs_map);
>
> Guess we should take rx_mcs_map as we are determining vht_rx_chains?
No, when we determine our needed RX chains, we need to know what the AP
can transmit to us, not what the AP can receive.
johannes
next prev parent reply other threads:[~2012-11-27 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 14:25 [PATCH 0/3] mac80211: VHT managed mode & radiotap support Johannes Berg
2012-11-26 14:25 ` [PATCH 1/3] cfg80211: rework chandef checking and export it Johannes Berg
2012-11-26 14:25 ` [PATCH 2/3] mac80211: support VHT association Johannes Berg
2012-11-27 12:12 ` Mahesh Palivela
2012-11-27 12:44 ` Johannes Berg [this message]
2012-11-26 14:25 ` [PATCH 3/3] mac80211: support (partial) VHT radiotap information Johannes Berg
2012-11-28 12:24 ` [PATCH 0/3] mac80211: VHT managed mode & radiotap support 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=1354020270.9576.8.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=maheshp@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