Given the size of those changes to brcmfmac -and considering that brcmfmac is shared among many targets (at least bcm27xx, bcm53xx, imx, rockchip, sunxi, x86_64)- you really want to see those tickle down through mainline/ wireless-next first, or you run a huge risk of regressions for anything but the RPi (and a major source of pain for future kernel- or mac80211 updates). And that's before even checking the licensing state of the changes and firmware blobs.