From: Kalle Valo <kvalo@codeaurora.org>
To: "Rafał Miłecki" <rafal@milecki.pl>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"Arend van Spriel" <arend.vanspriel@broadcom.com>,
"Franky Lin" <franky.lin@broadcom.com>,
"Hante Meuleman" <hante.meuleman@broadcom.com>,
"Chi-Hsien Lin" <chi-hsien.lin@cypress.com>,
"Wright Feng" <wright.feng@cypress.com>,
"Pieter-Paul Giesberts" <pieter-paul.giesberts@broadcom.com>,
"Chung-Hsien Hsu" <stanley.hsu@cypress.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com, stable@vger.kernel.org
Subject: Re: [PATCH FIX] brcmfmac: fix reporting support for 160 MHz channels
Date: Fri, 16 Nov 2018 10:40:02 +0200 [thread overview]
Message-ID: <87muq98lgd.fsf@codeaurora.org> (raw)
In-Reply-To: <f1e1160ba35a42e12a0162629be23304@milecki.pl> ("Rafał Miłecki"'s message of "Fri, 09 Nov 2018 21:10:56 +0100")
Rafał Miłecki <rafal@milecki.pl> writes:
> On 2018-11-09 15:05, Kalle Valo wrote:
>> Rafał Miłecki <zajec5@gmail.com> writes:
>>
>>> From: Rafał Miłecki <rafal@milecki.pl>
>>>
>>> Driver can report IEEE80211_VHT_CAP_SUPP_CHAN_WIDTH_160MHZ so it's
>>> important to provide valid & complete info about supported bands for
>>> each channel. By default no support for 160 MHz should be assumed
>>> unless
>>> firmware reports it for a given channel later.
>>>
>>> This fixes info passed to the userspace. Without that change userspace
>>> could try to use invalid channel and fail to start an interface.
>>>
>>> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
>>> Cc: stable@vger.kernel.org
>>
>> Should this be queued to 4.20?
>
> That's my suggestion.
Ok, I'll queue this for 4.20.
--
Kalle Valo
next prev parent reply other threads:[~2018-11-16 8:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 15:08 [PATCH FIX] brcmfmac: fix reporting support for 160 MHz channels Rafał Miłecki
2018-11-09 14:05 ` Kalle Valo
2018-11-09 20:10 ` Rafał Miłecki
2018-11-16 8:40 ` Kalle Valo [this message]
2018-11-16 8:46 ` wiki: tree labels in patches Kalle Valo
2018-11-16 8:49 ` Johannes Berg
2018-11-16 8:54 ` Kalle Valo
2018-11-16 8:55 ` Rafał Miłecki
2018-11-16 13:13 ` [PATCH FIX] brcmfmac: fix reporting support for 160 MHz channels Kalle Valo
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=87muq98lgd.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pieter-paul.giesberts@broadcom.com \
--cc=rafal@milecki.pl \
--cc=stable@vger.kernel.org \
--cc=stanley.hsu@cypress.com \
--cc=wright.feng@cypress.com \
--cc=zajec5@gmail.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).