Thread (37 messages) 37 messages, 4 authors, 2022-01-20

Re: [PATCH v3 3/9] brcmfmac: firmware: Do not crash on a NULL board_type

From: Arend van Spriel <arend.vanspriel@broadcom.com>
Date: 2022-01-20 13:38:00
Also in: linux-acpi, linux-devicetree, linux-wireless, lkml

On 1/20/2022 2:24 PM, Dmitry Osipenko wrote:
20.01.2022 16:23, Dmitry Osipenko пишет:
quoted
20.01.2022 11:29, Arend van Spriel пишет:
quoted
On 1/19/2022 11:02 PM, Dmitry Osipenko wrote:
quoted
17.01.2022 17:29, Hector Martin пишет:
quoted
This unbreaks support for USB devices, which do not have a board_type
to create an alt_path out of and thus were running into a NULL
dereference.

Fixes: 5ff013914c62 ("brcmfmac: firmware: Allow per-board firmware
binaries")
Signed-off-by: Hector Martin <redacted>
Technically, all patches that are intended to be included into next
stable kernel update require the "Cc: stable@vger.kernel.org" tag.
Being the nit picker that I am I would say it is recommended to safe
yourself extra work, not required, for the reason you give below.
Will be nice if stable tag could officially become a recommendation,
implying the stable tag. It's a requirement today, at least Greg KH
always demands to add it :)
*implying the stable tag if "fixes" tag presents.
I was a little confused reading your previous email in this thread. This 
makes a lot more sense :-p

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help