From: Johannes Berg <johannes@sipsolutions.net>
To: Filip Matusiak <filip.matusiak@tieto.com>,
linux-wireless@vger.kernel.org
Cc: marek.kwaczynski@tieto.com, davem@davemloft.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mac80211: Ignore VHT IE from peer with wrong rx_mcs_map
Date: Fri, 28 Oct 2016 17:46:00 +0200 [thread overview]
Message-ID: <1477669560.4220.1.camel@sipsolutions.net> (raw)
In-Reply-To: <1477665523-8970-1-git-send-email-filip.matusiak@tieto.com> (sfid-20161028_163919_221476_0288EF78)
On Fri, 2016-10-28 at 16:38 +0200, Filip Matusiak wrote:
> This is a workaround for VHT-enabled STAs which break the spec
> and have the VHT-MCS Rx map filled in with value 3 for all eight
> spacial streams.
>
> As per spec, in section 22.1.1 Introduction to the VHT PHY
> A VHT STA shall support at least single spactial stream VHT-MCSs
> 0 to 7 (transmit and receive) in all supported channel widths.
Interesting, and also kinda dumb :)
> + /*
> + * This is a workaround for VHT-enabled STAs which break the
>
I find that it helps, in the future, if we know an example of a station
that did this, so we can test other implementations etc. Can you change
the comment accordingly?
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Filip Matusiak
<filip.matusiak-++hxYGjEMp0AvxtiuMwx3w@public.gmane.org>,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: marek.kwaczynski-++hxYGjEMp0AvxtiuMwx3w@public.gmane.org,
davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] mac80211: Ignore VHT IE from peer with wrong rx_mcs_map
Date: Fri, 28 Oct 2016 17:46:00 +0200 [thread overview]
Message-ID: <1477669560.4220.1.camel@sipsolutions.net> (raw)
In-Reply-To: <1477665523-8970-1-git-send-email-filip.matusiak-++hxYGjEMp0AvxtiuMwx3w@public.gmane.org> (sfid-20161028_163919_221476_0288EF78)
On Fri, 2016-10-28 at 16:38 +0200, Filip Matusiak wrote:
> This is a workaround for VHT-enabled STAs which break the spec
> and have the VHT-MCS Rx map filled in with value 3 for all eight
> spacial streams.
>
> As per spec, in section 22.1.1 Introduction to the VHT PHY
> A VHT STA shall support at least single spactial stream VHT-MCSs
> 0 to 7 (transmit and receive) in all supported channel widths.
Interesting, and also kinda dumb :)
> + /*
> + * This is a workaround for VHT-enabled STAs which break the
>
I find that it helps, in the future, if we know an example of a station
that did this, so we can test other implementations etc. Can you change
the comment accordingly?
johannes
next prev parent reply other threads:[~2016-10-28 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 14:38 [PATCH] mac80211: Ignore VHT IE from peer with wrong rx_mcs_map Filip Matusiak
2016-10-28 15:46 ` Johannes Berg [this message]
2016-10-28 15:46 ` 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=1477669560.4220.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=filip.matusiak@tieto.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marek.kwaczynski@tieto.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.