From: Sasha Levin <sashal@kernel.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rafał Miłecki" <rafal@milecki.pl>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com, netdev@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 4.19 06/68] brcmutil: really fix decoding channel info for 160 MHz bandwidth
Date: Thu, 29 Nov 2018 11:54:56 -0500 [thread overview]
Message-ID: <20181129165456.GC208508@sasha-vm> (raw)
In-Reply-To: <87y39c85ns.fsf@purkki.adurom.net>
On Thu, Nov 29, 2018 at 01:49:43PM +0200, Kalle Valo wrote:
>Sasha Levin <sashal@kernel.org> writes:
>
>> From: Rafał Miłecki <rafal@milecki.pl>
>>
>> [ Upstream commit 3401d42c7ea2d064d15c66698ff8eb96553179ce ]
>>
>> Previous commit /adding/ support for 160 MHz chanspecs was incomplete.
>> It didn't set bandwidth info and didn't extract control channel info. As
>> the result it was also using uninitialized "sb" var.
>>
>> This change has been tested for two chanspecs found to be reported by
>> some devices/firmwares:
>> 1) 60/160 (0xee32)
>> Before: chnum:50 control_ch_num:36
>> After: chnum:50 control_ch_num:60
>> 2) 120/160 (0xed72)
>> Before: chnum:114 control_ch_num:100
>> After: chnum:114 control_ch_num:120
>>
>> Fixes: 330994e8e8ec ("brcmfmac: fix for proper support of 160MHz bandwidth")
>> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
>> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>
>Please mark your stable patches with:
>
>X-Patchwork-Hint: ignore
>
>This way patchwork ignores them and this saves my time. Thank you.
Will do, thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2018-11-29 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181129055559.159228-1-sashal@kernel.org>
2018-11-29 5:54 ` [PATCH AUTOSEL 4.19 06/68] brcmutil: really fix decoding channel info for 160 MHz bandwidth Sasha Levin
2018-11-29 11:49 ` Kalle Valo
2018-11-29 16:54 ` Sasha Levin [this message]
2018-11-29 5:54 ` [PATCH AUTOSEL 4.19 07/68] mt76: fix building without CONFIG_LEDS_CLASS Sasha Levin
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=20181129165456.GC208508@sasha-vm \
--to=sashal@kernel.org \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=stable@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