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

On Tue, 2021-04-13 at 10:39 +, Grumbach, Emmanuel wrote: > Hi, > > > > > Hi all, > > > > After merging the mac80211-next tree, today's linux-next build (htmldocs) > > produced this warning: > > > > include/net/cfg80211.h:6643: warning: expecting prototype for > >

RE: linux-next: build warning after merge of the mac80211-next tree

Hi, > > Hi all, > > After merging the mac80211-next tree, today's linux-next build (htmldocs) > produced this warning: > > include/net/cfg80211.h:6643: warning: expecting prototype for > wiphy_rfkill_set_hw_state(). Prototype was for > wiphy_rfkill_set_hw_state_reason() instead >

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

On Mon, 2020-11-09 at 16:43 +1100, Stephen Rothwell wrote: > Hi all, > > After merging the mac80211-next tree, today's linux-next build (htmldocs) > produced this warning: > > Documentation/driver-api/80211/cfg80211:48: include/net/cfg80211.h:1014: > WARNING: Unexpected indentation. >

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

Arnd Bergmann writes: > On Thu, May 24, 2018 at 6:11 AM, Kalle Valo wrote: >> Arnd Bergmann writes: >>> I also bisected this new warning to the same commit above: >>> >>> net/batman-adv/bat_v_elp.c: In function 'batadv_v_elp_get_throughput':

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

Arnd Bergmann writes: > On Thu, May 24, 2018 at 6:11 AM, Kalle Valo wrote: >> Arnd Bergmann writes: >>> I also bisected this new warning to the same commit above: >>> >>> net/batman-adv/bat_v_elp.c: In function 'batadv_v_elp_get_throughput': >>> net/batman-adv/bat_v_elp.c:154:1: warning: the

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

On Thu, May 24, 2018 at 6:11 AM, Kalle Valo wrote: > Arnd Bergmann writes: >> I also bisected this new warning to the same commit above: >> >> net/batman-adv/bat_v_elp.c: In function 'batadv_v_elp_get_throughput': >> net/batman-adv/bat_v_elp.c:154:1: warning:

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

On Thu, May 24, 2018 at 6:11 AM, Kalle Valo wrote: > Arnd Bergmann writes: >> I also bisected this new warning to the same commit above: >> >> net/batman-adv/bat_v_elp.c: In function 'batadv_v_elp_get_throughput': >> net/batman-adv/bat_v_elp.c:154:1: warning: the frame size of 1736 >> bytes is

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

Arnd Bergmann writes: > On Fri, May 11, 2018 at 2:20 PM, Kalle Valo wrote: >> Stephen Rothwell writes: >> >>> After merging the mac80211-next tree, today's linux-next build (arm_multi >>> v7_defconfig) produced this warning: >>> >>>

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

Arnd Bergmann writes: > On Fri, May 11, 2018 at 2:20 PM, Kalle Valo wrote: >> Stephen Rothwell writes: >> >>> After merging the mac80211-next tree, today's linux-next build (arm_multi >>> v7_defconfig) produced this warning: >>> >>> drivers/net/wireless/marvell/mwifiex/uap_event.c: In function

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

On Fri, May 11, 2018 at 2:20 PM, Kalle Valo wrote: > Stephen Rothwell writes: > >> After merging the mac80211-next tree, today's linux-next build (arm_multi >> v7_defconfig) produced this warning: >> >>

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

On Fri, May 11, 2018 at 2:20 PM, Kalle Valo wrote: > Stephen Rothwell writes: > >> After merging the mac80211-next tree, today's linux-next build (arm_multi >> v7_defconfig) produced this warning: >> >> drivers/net/wireless/marvell/mwifiex/uap_event.c: In function >>

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

Hi all, Just cc'ing the wireless list at Kalle's suggestion. On Wed, 9 May 2018 14:56:24 +1000 Stephen Rothwell wrote: > > Hi Johannes, > > After merging the mac80211-next tree, today's linux-next build (arm_multi > v7_defconfig) produced this warning: > >

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

Hi all, Just cc'ing the wireless list at Kalle's suggestion. On Wed, 9 May 2018 14:56:24 +1000 Stephen Rothwell wrote: > > Hi Johannes, > > After merging the mac80211-next tree, today's linux-next build (arm_multi > v7_defconfig) produced this warning: > >

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

Hi Kalle, On Fri, 11 May 2018 15:20:23 +0300 Kalle Valo wrote: > > Btw Stephen for mac80211 reports it would be a good idea to also cc > linux-wireless list, in case Johannes is not around etc. Thanks for the suggestion. Done. -- Cheers, Stephen Rothwell

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

Hi Kalle, On Fri, 11 May 2018 15:20:23 +0300 Kalle Valo wrote: > > Btw Stephen for mac80211 reports it would be a good idea to also cc > linux-wireless list, in case Johannes is not around etc. Thanks for the suggestion. Done. -- Cheers, Stephen Rothwell pgpWmdiByugpz.pgp Description:

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

Stephen Rothwell writes: > After merging the mac80211-next tree, today's linux-next build (arm_multi > v7_defconfig) produced this warning: > > drivers/net/wireless/marvell/mwifiex/uap_event.c: In function > 'mwifiex_process_uap_event': >

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

Stephen Rothwell writes: > After merging the mac80211-next tree, today's linux-next build (arm_multi > v7_defconfig) produced this warning: > > drivers/net/wireless/marvell/mwifiex/uap_event.c: In function > 'mwifiex_process_uap_event': > drivers/net/wireless/marvell/mwifiex/uap_event.c:333:1:

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

Thanks Stephen, The 0-day bot also gave me this heads-up, there are a few more places like it too. I'd asked Toke to fix the ones in the stack, but we both missed the ones in the drivers. I'll get a fix in for that one way or the other. johannes

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

Thanks Stephen, The 0-day bot also gave me this heads-up, there are a few more places like it too. I'd asked Toke to fix the ones in the stack, but we both missed the ones in the drivers. I'll get a fix in for that one way or the other. johannes