linux-next: build failure after merge of the mac80211-next tree

2020-11-10 Thread Stephen Rothwell
Hi all, After merging the mac80211-next tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/ath/ath9k/debug.c: In function 'read_file_misc': drivers/net/wireless/ath/ath9k/debug.c:741:35: error: 'struct ath9k_vif_iter_data' has no member named 'nwds' 741

Re: linux-next: build failure after merge of the mac80211-next tree

2020-04-28 Thread Sergey Matyukevich
> > Looks good. But I have a couple of questions: > > > > - why cleanup vif->mgmt_frame_reg in wilc_mac_open ? > > Otherwise wilc_update_mgmt_frame_registrations() will think there are no > changes whatsoever, and do nothing. > > > - previously wilc_wfi_p2p_rx was called only for PROBE_REQ and A

Re: linux-next: build failure after merge of the mac80211-next tree

2020-04-28 Thread Johannes Berg
On Tue, 2020-04-28 at 10:45 +0300, Sergey Matyukevich wrote: > > Looks good. But I have a couple of questions: > > - why cleanup vif->mgmt_frame_reg in wilc_mac_open ? Otherwise wilc_update_mgmt_frame_registrations() will think there are no changes whatsoever, and do nothing. > - previously wil

Re: linux-next: build failure after merge of the mac80211-next tree

2020-04-28 Thread Sergey Matyukevich
On Tue, Apr 28, 2020 at 09:24:16AM +0200, Johannes Berg wrote: > On Tue, 2020-04-28 at 10:25 +0300, Sergey Matyukevich wrote: > > On Tue, Apr 28, 2020 at 09:01:30AM +0200, Johannes Berg wrote: > > > On Tue, 2020-04-28 at 12:29 +1000, Stephen Rothwell wrote: > > > > Hi all, > > > > > > > > After me

Re: linux-next: build failure after merge of the mac80211-next tree

2020-04-28 Thread Johannes Berg
On Tue, 2020-04-28 at 10:25 +0300, Sergey Matyukevich wrote: > On Tue, Apr 28, 2020 at 09:01:30AM +0200, Johannes Berg wrote: > > On Tue, 2020-04-28 at 12:29 +1000, Stephen Rothwell wrote: > > > Hi all, > > > > > > After merging the mac80211-next tree, today's linux-next build (x86_64 > > > allmod

Re: linux-next: build failure after merge of the mac80211-next tree

2020-04-28 Thread Sergey Matyukevich
On Tue, Apr 28, 2020 at 09:01:30AM +0200, Johannes Berg wrote: > On Tue, 2020-04-28 at 12:29 +1000, Stephen Rothwell wrote: > > Hi all, > > > > After merging the mac80211-next tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > Caused by commit > > > > 6cd536fe62

Re: linux-next: build failure after merge of the mac80211-next tree

2020-04-28 Thread Johannes Berg
On Tue, 2020-04-28 at 12:29 +1000, Stephen Rothwell wrote: > Hi all, > > After merging the mac80211-next tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > Caused by commit > > 6cd536fe62ef ("cfg80211: change internal management frame registration API") Yeah. I forgo

Re: linux-next: build failure after merge of the mac80211-next tree

2017-12-12 Thread Toke Høiland-Jørgensen
Kalle Valo writes: > Toke Høiland-Jørgensen writes: > >>> Sorry for the inconvenience, I hadn't realized mt76 went in now. >> >> Yeah, hadn't expected these streams to cross either. > > I did ask[1] if everyone are ok that I apply mt76 and I didn't get any > comments, Huh, did actually see that

Re: linux-next: build failure after merge of the mac80211-next tree

2017-12-12 Thread Kalle Valo
Toke Høiland-Jørgensen writes: >> Sorry for the inconvenience, I hadn't realized mt76 went in now. > > Yeah, hadn't expected these streams to cross either. I did ask[1] if everyone are ok that I apply mt76 and I didn't get any comments, I guess I need to make more noise next time when I'm applyi

Re: linux-next: build failure after merge of the mac80211-next tree

2017-12-12 Thread Toke Høiland-Jørgensen
Johannes Berg writes: > Hi Stephen, > > Thanks! > > Felix made me aware of this yesterday evening and said he's going to > work out the required changes to mt76. > > Kalle and I will make sure to submit the trees to Dave one by one so he > doesn't have to deal with it :) > > Unfortunately, this m

Re: linux-next: build failure after merge of the mac80211-next tree

2017-12-12 Thread Johannes Berg
Hi Stephen, Thanks! Felix made me aware of this yesterday evening and said he's going to work out the required changes to mt76. Kalle and I will make sure to submit the trees to Dave one by one so he doesn't have to deal with it :) Unfortunately, this might take a few days to resolve. > -void

linux-next: build failure after merge of the mac80211-next tree

2017-12-11 Thread Stephen Rothwell
Hi Johannes, After merging the mac80211-next tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/mediatek/mt76/mt76x2_main.c:539:19: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .wake_tx_queue = mt76_wake_tx_q

Re: linux-next: build failure after merge of the mac80211-next tree

2016-02-24 Thread Johannes Berg
Hi Stephen, > [...] > include/linux/bug.h:74:2: note: in expansion of macro > 'BUILD_BUG_ON_MSG' >   BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition) >   ^ > net/rfkill/core.c:647:2: note: in expansion of macro 'BUILD_BUG_ON' >   BUILD_BUG_ON(!rfkill_types[NUM_RFKILL_TYPES - 1]); >

linux-next: build failure after merge of the mac80211-next tree

2016-02-23 Thread Stephen Rothwell
Hi Johannes, After merging the mac80211-next tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/linkage.h:4:0, from include/linux/kernel.h:6, from net/rfkill/core.c:20: net/rfkill/core.c: In function 'rfkill