Re: nl80211 wlcore regression in next

2019-07-23 Thread Tony Lindgren
* Johannes Berg [190723 05:08]: > Hi, > > > Looks like this one crept back as the fix is missing from v5.3-rc1. > > > > Forgot to include in the pull request? > > More like forgot to send the pull request, my bad. I eventually realized > a couple of days ago and it'll be coming upstream soon.

Re: nl80211 wlcore regression in next

2019-07-22 Thread Johannes Berg
Hi, > Looks like this one crept back as the fix is missing from v5.3-rc1. > > Forgot to include in the pull request? More like forgot to send the pull request, my bad. I eventually realized a couple of days ago and it'll be coming upstream soon. Sorry about that. johannes

Re: nl80211 wlcore regression in next

2019-07-22 Thread Tony Lindgren
Hi, * Johannes Berg [190625 08:03]: > On Tue, 2019-06-25 at 01:00 -0700, Tony Lindgren wrote: > > Hi, > > > > * Johannes Berg [190625 07:47]: > > > On Tue, 2019-06-25 at 00:38 -0700, Tony Lindgren wrote: > > > > Hi, > > > > > > > > Looks like at least drivers/net/wireless/ti wlcore driver has

Re: nl80211 wlcore regression in next

2019-06-25 Thread Kalle Valo
Tony Lindgren writes: > Hi, > > * Johannes Berg [190625 07:47]: >> On Tue, 2019-06-25 at 00:38 -0700, Tony Lindgren wrote: >> > Hi, >> > >> > Looks like at least drivers/net/wireless/ti wlcore driver has stopped >> > working in Linux next with commit 901bb9891855 ("nl80211: require and >> >

Re: nl80211 wlcore regression in next

2019-06-25 Thread Johannes Berg
Hi Arend, > By chance noticed the patch included brcmfmac. So I tried, but I get > compile issue below. It is because ERR_PTR really is an inline function > so that is not working. So also need to patch that. I left the extra > braces around the error code although not strictly necessary.

Re: nl80211 wlcore regression in next

2019-06-25 Thread Arend Van Spriel
On 6/25/2019 10:02 AM, Johannes Berg wrote: On Tue, 2019-06-25 at 01:00 -0700, Tony Lindgren wrote: Hi, * Johannes Berg [190625 07:47]: On Tue, 2019-06-25 at 00:38 -0700, Tony Lindgren wrote: Hi, Looks like at least drivers/net/wireless/ti wlcore driver has stopped working in Linux next

Re: nl80211 wlcore regression in next

2019-06-25 Thread Johannes Berg
On Tue, 2019-06-25 at 01:00 -0700, Tony Lindgren wrote: > Hi, > > * Johannes Berg [190625 07:47]: > > On Tue, 2019-06-25 at 00:38 -0700, Tony Lindgren wrote: > > > Hi, > > > > > > Looks like at least drivers/net/wireless/ti wlcore driver has stopped > > > working in Linux next with commit

Re: nl80211 wlcore regression in next

2019-06-25 Thread Tony Lindgren
Hi, * Johannes Berg [190625 07:47]: > On Tue, 2019-06-25 at 00:38 -0700, Tony Lindgren wrote: > > Hi, > > > > Looks like at least drivers/net/wireless/ti wlcore driver has stopped > > working in Linux next with commit 901bb9891855 ("nl80211: require and > > validate vendor command policy").

Re: nl80211 wlcore regression in next

2019-06-25 Thread Johannes Berg
On Tue, 2019-06-25 at 00:38 -0700, Tony Lindgren wrote: > Hi, > > Looks like at least drivers/net/wireless/ti wlcore driver has stopped > working in Linux next with commit 901bb9891855 ("nl80211: require and > validate vendor command policy"). Reverting the commit above makes it > work again. >

nl80211 wlcore regression in next

2019-06-25 Thread Tony Lindgren
Hi, Looks like at least drivers/net/wireless/ti wlcore driver has stopped working in Linux next with commit 901bb9891855 ("nl80211: require and validate vendor command policy"). Reverting the commit above makes it work again. It fails with the warning below, any ideas what goes wrong? Regards,