[PATCH 0/8] brcmfmac: event handling and other fixes
This series provides the following: * avoid unexpected firmware events. * allow passing events explicitly for PCIe and SDIO devices. * fix issue with boardrev entry in nvram. * fix for wowl. * fix possible null pointer access upon aborting p2p scan. The series is intended for v4.7 kernel and applies to the master branch of the wireless-drivers-next repository. Arend van Spriel (3): brcmfmac: cleanup ampdu-rx host reorder code brcmfmac: revise handling events in receive path brcmfmac: create common function for handling brcmf_proto_hdrpull() Franky Lin (1): brcmfmac: screening firmware event packet Hante Meuleman (4): brcmfmac: clear eventmask array before using it brcmfmac: fix clearing wowl wake indicators brcmfmac: insert default boardrev in nvram data if missing brcmfmac: fix p2p scan abort null pointer exception .../wireless/broadcom/brcm80211/brcmfmac/bcdc.c| 7 + .../net/wireless/broadcom/brcm80211/brcmfmac/bus.h | 4 +- .../broadcom/brcm80211/brcmfmac/cfg80211.c | 3 +- .../wireless/broadcom/brcm80211/brcmfmac/core.c| 247 +++-- .../wireless/broadcom/brcm80211/brcmfmac/core.h| 4 - .../broadcom/brcm80211/brcmfmac/firmware.c | 30 ++- .../wireless/broadcom/brcm80211/brcmfmac/fweh.c| 1 + .../broadcom/brcm80211/brcmfmac/fwsignal.c | 209 + .../broadcom/brcm80211/brcmfmac/fwsignal.h | 1 + .../wireless/broadcom/brcm80211/brcmfmac/msgbuf.c | 46 ++-- .../net/wireless/broadcom/brcm80211/brcmfmac/p2p.c | 2 +- .../wireless/broadcom/brcm80211/brcmfmac/proto.h | 16 ++ .../wireless/broadcom/brcm80211/brcmfmac/sdio.c| 32 ++- .../net/wireless/broadcom/brcm80211/brcmfmac/usb.c | 2 +- 14 files changed, 352 insertions(+), 252 deletions(-) -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 0/8] brcmfmac: event handling and other fixes
On 11 April 2016 at 11:35, Arend van Spriel wrote: > This series provides the following: > > * avoid unexpected firmware events. > * allow passing events explicitly for PCIe and SDIO devices. > * fix issue with boardrev entry in nvram. > * fix for wowl. > * fix possible null pointer access upon aborting p2p scan. > > The series is intended for v4.7 kernel and applies to the master > branch of the wireless-drivers-next repository. Hey Arend, Unfortunately I'm finding all your recent messages in spam :( It seems GMail doesn't like something about the Broadcom server: "Why is this message in Spam? It has a from address in broadcom.com but has failed broadcom.com's required tests for authentication. Learn more" Quoted "Learn more" text links to the: https://support.google.com/mail/answer/1366858?hl=en-GB&expand=5 Do you think you can point it to sb at Broadcom? -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 0/8] brcmfmac: event handling and other fixes
On 11-04-16 13:20, Rafał Miłecki wrote: > On 11 April 2016 at 11:35, Arend van Spriel wrote: >> This series provides the following: >> >> * avoid unexpected firmware events. >> * allow passing events explicitly for PCIe and SDIO devices. >> * fix issue with boardrev entry in nvram. >> * fix for wowl. >> * fix possible null pointer access upon aborting p2p scan. >> >> The series is intended for v4.7 kernel and applies to the master >> branch of the wireless-drivers-next repository. > > Hey Arend, > > Unfortunately I'm finding all your recent messages in spam :( It seems > GMail doesn't like something about the Broadcom server: > "Why is this message in Spam? It has a from address in broadcom.com > but has failed broadcom.com's required tests for authentication. Learn > more" > Quoted "Learn more" text links to the: > https://support.google.com/mail/answer/1366858?hl=en-GB&expand=5 > > Do you think you can point it to sb at Broadcom? sb? Help me understand this and I may have an appropriate answer :-p Broadcom actually moved to Google Apps. I am still using my old email address and smtp server for submitting patches. Maybe that is the issue here. Regards, Arend -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 0/8] brcmfmac: event handling and other fixes
Hi Arend, On Tue, Apr 12, 2016 at 6:55 PM, Arend van Spriel wrote: > On 11-04-16 13:20, Rafał Miłecki wrote: >> On 11 April 2016 at 11:35, Arend van Spriel wrote: >>> This series provides the following: >>> >>> * avoid unexpected firmware events. >>> * allow passing events explicitly for PCIe and SDIO devices. >>> * fix issue with boardrev entry in nvram. >>> * fix for wowl. >>> * fix possible null pointer access upon aborting p2p scan. >>> >>> The series is intended for v4.7 kernel and applies to the master >>> branch of the wireless-drivers-next repository. >> >> Hey Arend, >> >> Unfortunately I'm finding all your recent messages in spam :( It seems >> GMail doesn't like something about the Broadcom server: >> "Why is this message in Spam? It has a from address in broadcom.com >> but has failed broadcom.com's required tests for authentication. Learn >> more" >> Quoted "Learn more" text links to the: >> https://support.google.com/mail/answer/1366858?hl=en-GB&expand=5 >> >> Do you think you can point it to sb at Broadcom? > > sb? Help me understand this and I may have an appropriate answer :-p > > Broadcom actually moved to Google Apps. I am still using my old email > address and smtp server for submitting patches. Maybe that is the issue > here. That's the issue. IIRC this happens because the emails are missing some header that authenticates them as actually being from broadcom.com. (I get this all the time when sending Debian bug reports through my personal SMTP server.) Thanks, -- Julian Calaby Email: julian.cal...@gmail.com Profile: http://www.google.com/profiles/julian.calaby/ -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html