Re: [v2,01/10] qtnfmac: check that MAC exists in regulatory notifier

Sergey Matyukevich [off-list ref] writes:

Thanks Kalle,

quoted

quoted

It is possible that regulatory notifier is called before MAC data
was allocated. We need to verify that MAC data exists before trying
to send a regulatory change event.

Signed-off-by: Igor Mitsyanko <redacted>

10 patches applied to wireless-drivers-next.git, thanks.

4fd045cdb239 qtnfmac: check that MAC exists in regulatory notifier
5bf374ab91ad qtnfmac: pass complete channel data between driver and firmware
b05ee456fd21 qtnfmac: add support for radar detection and CAC
e6ef8cd05145 qtnfmac: change default interface mode from AP to STA
e6e594aff26a qtnfmac: check for passed channel being NULL in MGMT_TX command
fbad963a28e4 qtnfmac: fix rssi data passed to wireless core
9cbd599966d8 qtnfmac: fill wiphy's extended capabilities
4d2a7a1cfa68 qtnfmac: modify GET_STA_STATS cmd format for back/forward compatibility
7a4d3a3bc84e qtnfmac: keeping track of "generation" for STA info
f1398fd2dd8c qtnfmac: support MAC address based access control

Just to understand the timelines... Could you please clarify if these patches
are still going to make it into 4.16 merge window ?

They should, but of course I can't promise anything.

My deadline is that when merge window opens the patches need to be in
net-next. You can follow the predictions for the schedule here:

http://phb-crystal-ball.org/

-- 
Kalle Valo