Linux wireless drivers development
 help / color / mirror / Atom feed
From: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH v2] mac80211: fix RX STBC override byte order
Date: Tue, 9 Apr 2019 14:55:22 +0000	[thread overview]
Message-ID: <20190409145515.kq54n3ca3qukw6du@bars> (raw)
In-Reply-To: <20190409121120.7962-1-johannes@sipsolutions.net>

> The original patch neglected to take byte order conversions
> into account, fix that.
> 
> Fixes: d9bb410888ce ("mac80211: allow overriding HT STBC capabilities")
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
>  net/mac80211/ht.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/net/mac80211/ht.c b/net/mac80211/ht.c
> index e03c46ac8e4d..c62101857b9b 100644
> --- a/net/mac80211/ht.c
> +++ b/net/mac80211/ht.c
> @@ -112,8 +112,9 @@ void ieee80211_apply_htcap_overrides(struct ieee80211_sub_if_data *sdata,
>                              IEEE80211_HT_CAP_TX_STBC);
> 
>         /* Allow user to configure RX STBC bits */
> -       if (ht_capa_mask->cap_info & IEEE80211_HT_CAP_RX_STBC)
> -               ht_cap->cap |= ht_capa->cap_info & IEEE80211_HT_CAP_RX_STBC;
> +       if (ht_capa_mask->cap_info & cpu_to_le16(IEEE80211_HT_CAP_RX_STBC))
> +               ht_cap->cap |= le16_to_cpu(ht_capa->cap_info) &
> +                                       IEEE80211_HT_CAP_RX_STBC;
> 
>         /* Allow user to decrease AMPDU factor */
>         if (ht_capa_mask->ampdu_params_info &

Thanks for fixing this!

Reviewed-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>

Regards,
Sergey

      reply	other threads:[~2019-04-09 14:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 12:11 [PATCH v2] mac80211: fix RX STBC override byte order Johannes Berg
2019-04-09 14:55 ` Sergey Matyukevich [this message]

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=20190409145515.kq54n3ca3qukw6du@bars \
    --to=sergey.matyukevich.os@quantenna.com \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox