From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Levin 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 Message-ID: <20181129165456.GC208508@sasha-vm> References: <20181129055559.159228-1-sashal@kernel.org> <20181129055559.159228-6-sashal@kernel.org> <87y39c85ns.fsf@purkki.adurom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org, =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= , linux-wireless@vger.kernel.org, brcm80211-dev-list.pdl@broadcom.com, brcm80211-dev-list@cypress.com, netdev@vger.kernel.org To: Kalle Valo Return-path: Content-Disposition: inline In-Reply-To: <87y39c85ns.fsf@purkki.adurom.net> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thu, Nov 29, 2018 at 01:49:43PM +0200, Kalle Valo wrote: >Sasha Levin writes: > >> From: Rafał Miłecki >> >> [ 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 >> Signed-off-by: Kalle Valo >> Signed-off-by: Sasha Levin > >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