Re: [PATCH] wireless: fix bogus maybe-uninitialized warning

2016-11-09 Thread Arnd Bergmann
On Wednesday, November 9, 2016 9:10:46 AM CET Johannes Berg wrote: > > > Ideally we prefer that drivers/net/wireless and net/wireless changes > > are > > split into different patches as they get applied to different trees. Ok, good to know. I had split out the drivers/staging changes, but wasn't

Re: [PATCH] wireless: fix bogus maybe-uninitialized warning

2016-11-09 Thread Johannes Berg
> Ideally we prefer that drivers/net/wireless and net/wireless changes > are > split into different patches as they get applied to different trees. > Johannes, is it ok if I take this change through my tree this time? Sure, please do, thanks. (I don't particularly care about the lib80211 stuff a

Re: [PATCH] wireless: fix bogus maybe-uninitialized warning

2016-11-08 Thread Kalle Valo
Arnd Bergmann writes: > The hostap_80211_rx() function is supposed to set up the mac addresses > for four possible cases, based on two bits of input data. For > some reason, gcc decides that it's possible that none of the these > four cases apply and the addresses remain uninitialized: > > driver

[PATCH] wireless: fix bogus maybe-uninitialized warning

2016-10-24 Thread Arnd Bergmann
The hostap_80211_rx() function is supposed to set up the mac addresses for four possible cases, based on two bits of input data. For some reason, gcc decides that it's possible that none of the these four cases apply and the addresses remain uninitialized: drivers/net/wireless/intersil/hostap/host