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

Stephen Rothwell writes: > After merging the wireless-drivers-next tree, today's linux-next build > (powerpc allyesconfig) failed like this: > > ld: drivers/net/wireless/realtek/rtw88/rtw8822ce.o:(.rodata.rtw_pm_ops+0x0): > multiple definition of `rtw_pm_ops'; >

linux-next: build failure after merge of the wireless-drivers-next tree

Hi all, After merging the wireless-drivers-next tree, today's linux-next build (powerpc allyesconfig) failed like this: ld: drivers/net/wireless/realtek/rtw88/rtw8822ce.o:(.rodata.rtw_pm_ops+0x0): multiple definition of `rtw_pm_ops';

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

Hi Dave, On Thu, 15 Jun 2017 12:08:08 -0400 (EDT) David Miller wrote: > > From: Stephen Rothwell > Date: Tue, 13 Jun 2017 12:00:24 +1000 > > > On Thu, 8 Jun 2017 12:27:59 +1000 Stephen Rothwell > > wrote: > >> > >> After

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

Hi Dave, On Thu, 15 Jun 2017 12:08:08 -0400 (EDT) David Miller wrote: > > From: Stephen Rothwell > Date: Tue, 13 Jun 2017 12:00:24 +1000 > > > On Thu, 8 Jun 2017 12:27:59 +1000 Stephen Rothwell > > wrote: > >> > >> After merging the wireless-drivers-next tree, today's linux-next build >

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

From: Stephen Rothwell Date: Tue, 13 Jun 2017 12:00:24 +1000 > Hi Dave, > > On Thu, 8 Jun 2017 12:27:59 +1000 Stephen Rothwell > wrote: >> >> After merging the wireless-drivers-next tree, today's linux-next build >> (x86_64 allmodconfig) failed

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

From: Stephen Rothwell Date: Tue, 13 Jun 2017 12:00:24 +1000 > Hi Dave, > > On Thu, 8 Jun 2017 12:27:59 +1000 Stephen Rothwell > wrote: >> >> After merging the wireless-drivers-next tree, today's linux-next build >> (x86_64 allmodconfig) failed like this: >> >>

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

Hi Dave, On Thu, 8 Jun 2017 12:27:59 +1000 Stephen Rothwell wrote: > > After merging the wireless-drivers-next tree, today's linux-next build > (x86_64 allmodconfig) failed like this: > > drivers/net/wireless/quantenna/qtnfmac/core.c: In function >

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

Hi Dave, On Thu, 8 Jun 2017 12:27:59 +1000 Stephen Rothwell wrote: > > After merging the wireless-drivers-next tree, today's linux-next build > (x86_64 allmodconfig) failed like this: > > drivers/net/wireless/quantenna/qtnfmac/core.c: In function > 'qtnf_core_net_attach': >

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

Hi Kalle, On Thu, 08 Jun 2017 15:07:00 +0300 Kalle Valo wrote: > > Stephen Rothwell writes: > > > On Wed, 7 Jun 2017 19:43:18 -0700 Igor Mitsyanko > > wrote: > >> > >> thanks. As I understand, you've applied this

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

Hi Kalle, On Thu, 08 Jun 2017 15:07:00 +0300 Kalle Valo wrote: > > Stephen Rothwell writes: > > > On Wed, 7 Jun 2017 19:43:18 -0700 Igor Mitsyanko > > wrote: > >> > >> thanks. As I understand, you've applied this patch during a merge and no > >> further actions are required, correct? >

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

Stephen Rothwell writes: > Hi Igor, > > On Wed, 7 Jun 2017 19:43:18 -0700 Igor Mitsyanko > wrote: >> >> thanks. As I understand, you've applied this patch during a merge and no >> further actions are required, correct? > > Dave Miller

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

Stephen Rothwell writes: > Hi Igor, > > On Wed, 7 Jun 2017 19:43:18 -0700 Igor Mitsyanko > wrote: >> >> thanks. As I understand, you've applied this patch during a merge and no >> further actions are required, correct? > > Dave Miller will need to apply that patch (or something similar) when

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

Hi Igor, On Wed, 7 Jun 2017 19:43:18 -0700 Igor Mitsyanko wrote: > > thanks. As I understand, you've applied this patch during a merge and no > further actions are required, correct? Dave Miller will need to apply that patch (or something similar) when he

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

Hi Igor, On Wed, 7 Jun 2017 19:43:18 -0700 Igor Mitsyanko wrote: > > thanks. As I understand, you've applied this patch during a merge and no > further actions are required, correct? Dave Miller will need to apply that patch (or something similar) when he merges the wireless-drivers-next tree

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

On 06/07/2017 07:27 PM, Stephen Rothwell wrote: External Email Hi all, After merging the wireless-drivers-next tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/quantenna/qtnfmac/core.c: In function 'qtnf_core_net_attach':

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

On 06/07/2017 07:27 PM, Stephen Rothwell wrote: External Email Hi all, After merging the wireless-drivers-next tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/quantenna/qtnfmac/core.c: In function 'qtnf_core_net_attach':

linux-next: build failure after merge of the wireless-drivers-next tree

Hi all, After merging the wireless-drivers-next tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/quantenna/qtnfmac/core.c: In function 'qtnf_core_net_attach': drivers/net/wireless/quantenna/qtnfmac/core.c:319:5: error: 'struct net_device' has no

linux-next: build failure after merge of the wireless-drivers-next tree

Hi all, After merging the wireless-drivers-next tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/quantenna/qtnfmac/core.c: In function 'qtnf_core_net_attach': drivers/net/wireless/quantenna/qtnfmac/core.c:319:5: error: 'struct net_device' has no

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

Brian Norris writes: > Just to head this off, since I noticed it... > > On Tue, Jul 19, 2016 at 05:08:59PM +0300, Kalle Valo wrote: >> Rafał Miłecki writes: >> > I sent a patch seconds ago, you may just take a look at it. If you >> > still prefer

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

Brian Norris writes: > Just to head this off, since I noticed it... > > On Tue, Jul 19, 2016 at 05:08:59PM +0300, Kalle Valo wrote: >> Rafał Miłecki writes: >> > I sent a patch seconds ago, you may just take a look at it. If you >> > still prefer to revert my commit, go ahead. >> >> Ok, let's

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

Hi Brian, On Tue, 19 Jul 2016 11:39:13 -0700 Brian Norris wrote: > > I applied a trivial change to this same Kconfig entry: > > Subject: mtd: update description of MTD_BCM47XXSFLASH symbol >

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

Hi Brian, On Tue, 19 Jul 2016 11:39:13 -0700 Brian Norris wrote: > > I applied a trivial change to this same Kconfig entry: > > Subject: mtd: update description of MTD_BCM47XXSFLASH symbol > http://git.infradead.org/l2-mtd.git/commitdiff/0a526341fee054c1e2b9f0e4b2b424ae81707d4c > > It's a

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

Just to head this off, since I noticed it... On Tue, Jul 19, 2016 at 05:08:59PM +0300, Kalle Valo wrote: > Rafał Miłecki writes: > > I sent a patch seconds ago, you may just take a look at it. If you > > still prefer to revert my commit, go ahead. > > Ok, let's try your fix.

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

Just to head this off, since I noticed it... On Tue, Jul 19, 2016 at 05:08:59PM +0300, Kalle Valo wrote: > Rafał Miłecki writes: > > I sent a patch seconds ago, you may just take a look at it. If you > > still prefer to revert my commit, go ahead. > > Ok, let's try your fix. We still have few

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

Rafał Miłecki writes: > On 19 July 2016 at 09:09, Kalle Valo wrote: >> Rafał Miłecki writes: >> >>> On 19 July 2016 at 08:30, Kalle Valo wrote: Stephen Rothwell writes: >

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

Rafał Miłecki writes: > On 19 July 2016 at 09:09, Kalle Valo wrote: >> Rafał Miłecki writes: >> >>> On 19 July 2016 at 08:30, Kalle Valo wrote: Stephen Rothwell writes: > After merging the wireless-drivers-next tree, today's linux-next build > (powerpc allyesconfig) failed

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

On 19 July 2016 at 09:09, Kalle Valo wrote: > Rafał Miłecki writes: > >> On 19 July 2016 at 08:30, Kalle Valo wrote: >>> Stephen Rothwell writes: >>> After merging the wireless-drivers-next tree, today's

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

On 19 July 2016 at 09:09, Kalle Valo wrote: > Rafał Miłecki writes: > >> On 19 July 2016 at 08:30, Kalle Valo wrote: >>> Stephen Rothwell writes: >>> After merging the wireless-drivers-next tree, today's linux-next build (powerpc allyesconfig) failed like this:

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

Rafał Miłecki writes: > On 19 July 2016 at 08:30, Kalle Valo wrote: >> Stephen Rothwell writes: >> >>> After merging the wireless-drivers-next tree, today's linux-next build >>> (powerpc allyesconfig) failed like this: >>> >>>

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

Rafał Miłecki writes: > On 19 July 2016 at 08:30, Kalle Valo wrote: >> Stephen Rothwell writes: >> >>> After merging the wireless-drivers-next tree, today's linux-next build >>> (powerpc allyesconfig) failed like this: >>> >>> drivers/mtd/devices/bcm47xxsflash.c: In function

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

On 19 July 2016 at 08:30, Kalle Valo wrote: > Stephen Rothwell writes: > >> After merging the wireless-drivers-next tree, today's linux-next build >> (powerpc allyesconfig) failed like this: >> >> drivers/mtd/devices/bcm47xxsflash.c: In function

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

On 19 July 2016 at 08:30, Kalle Valo wrote: > Stephen Rothwell writes: > >> After merging the wireless-drivers-next tree, today's linux-next build >> (powerpc allyesconfig) failed like this: >> >> drivers/mtd/devices/bcm47xxsflash.c: In function 'bcm47xxsflash_bcma_probe': >>

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

Stephen Rothwell writes: > After merging the wireless-drivers-next tree, today's linux-next build > (powerpc allyesconfig) failed like this: > > drivers/mtd/devices/bcm47xxsflash.c: In function 'bcm47xxsflash_bcma_probe': > drivers/mtd/devices/bcm47xxsflash.c:299:17:

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

Stephen Rothwell writes: > After merging the wireless-drivers-next tree, today's linux-next build > (powerpc allyesconfig) failed like this: > > drivers/mtd/devices/bcm47xxsflash.c: In function 'bcm47xxsflash_bcma_probe': > drivers/mtd/devices/bcm47xxsflash.c:299:17: error: implicit declaration

linux-next: build failure after merge of the wireless-drivers-next tree

Hi all, After merging the wireless-drivers-next tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/mtd/devices/bcm47xxsflash.c: In function 'bcm47xxsflash_bcma_probe': drivers/mtd/devices/bcm47xxsflash.c:299:17: error: implicit declaration of function

linux-next: build failure after merge of the wireless-drivers-next tree

Hi all, After merging the wireless-drivers-next tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/mtd/devices/bcm47xxsflash.c: In function 'bcm47xxsflash_bcma_probe': drivers/mtd/devices/bcm47xxsflash.c:299:17: error: implicit declaration of function

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

Stephen Rothwell writes: > After merging the wireless-drivers-next tree, today's linux-next build > failed the same way as the net-next tree did yesterday (suprise! :-)). > > I have used the version from next-20160218 for today. Yeah, not a surprise as yesterday I fast

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

Stephen Rothwell writes: > After merging the wireless-drivers-next tree, today's linux-next build > failed the same way as the net-next tree did yesterday (suprise! :-)). > > I have used the version from next-20160218 for today. Yeah, not a surprise as yesterday I fast forwarded

linux-next: build failure after merge of the wireless-drivers-next tree

Hi Kalle, After merging the wireless-drivers-next tree, today's linux-next build failed the same way as the net-next tree did yesterday (suprise! :-)). I have used the version from next-20160218 for today. -- Cheers, Stephen Rothwell

linux-next: build failure after merge of the wireless-drivers-next tree

Hi Kalle, After merging the wireless-drivers-next tree, today's linux-next build failed the same way as the net-next tree did yesterday (suprise! :-)). I have used the version from next-20160218 for today. -- Cheers, Stephen Rothwell

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

Hi Stephen, Stephen Rothwell writes: > After merging the wireless-drivers-next tree, today's linux-next build > (x86_64 allmodconfig) failed like this: > > drivers/net/wireless/ath/ath9k/debug_sta.c: In function 'read_file_node_aggr': > drivers/net/wireless/ath/ath9k/debug_sta.c:54:25: error:

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

Hi Stephen, Stephen Rothwell s...@canb.auug.org.au writes: After merging the wireless-drivers-next tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/ath/ath9k/debug_sta.c: In function 'read_file_node_aggr':

linux-next: build failure after merge of the wireless-drivers-next tree

Hi Kalle, After merging the wireless-drivers-next tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/ath/ath9k/debug_sta.c: In function 'read_file_node_aggr': drivers/net/wireless/ath/ath9k/debug_sta.c:54:25: error: 'struct ath_node' has no member named

linux-next: build failure after merge of the wireless-drivers-next tree

Hi Kalle, After merging the wireless-drivers-next tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/ath/ath9k/debug_sta.c: In function 'read_file_node_aggr': drivers/net/wireless/ath/ath9k/debug_sta.c:54:25: error: 'struct ath_node' has no member named

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

Hi Kalle, On Mon, 27 Jul 2015 08:41:49 +0300 Kalle Valo wrote: > > Stephen Rothwell writes: > > > After merging the wireless-drivers-next tree, today's linux-next build > > (x86_64 allmodconfig) failed like this: > > > > ERROR: "of_default_bus_match_table" [drivers/bcma/bcma.ko] undefined! > >

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

Hi Kalle, On Mon, 27 Jul 2015 08:41:49 +0300 Kalle Valo kv...@codeaurora.org wrote: Stephen Rothwell s...@canb.auug.org.au writes: After merging the wireless-drivers-next tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: of_default_bus_match_table

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

Hi Stephen, Stephen Rothwell writes: > After merging the wireless-drivers-next tree, today's linux-next build > (x86_64 allmodconfig) failed like this: > > ERROR: "of_default_bus_match_table" [drivers/bcma/bcma.ko] undefined! > > Caused by commit > > cae761b5a6bd ("bcma: populate bus DT

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

Hi Stephen, Stephen Rothwell s...@canb.auug.org.au writes: After merging the wireless-drivers-next tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: of_default_bus_match_table [drivers/bcma/bcma.ko] undefined! Caused by commit cae761b5a6bd (bcma: populate

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

Hi Stephen, Stephen Rothwell writes: > After merging the wireless-drivers-next tree, today's linux-next build > (x86_64 allmodconfig) failed like this: > > ERROR: "of_default_bus_match_table" [drivers/bcma/bcma.ko] undefined! > > Caused by commit > > cae761b5a6bd ("bcma: populate bus DT

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

Hi Stephen, Stephen Rothwell s...@canb.auug.org.au writes: After merging the wireless-drivers-next tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: of_default_bus_match_table [drivers/bcma/bcma.ko] undefined! Caused by commit cae761b5a6bd (bcma: populate

linux-next: build failure after merge of the wireless-drivers-next tree

Hi Kalle, After merging the wireless-drivers-next tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "of_default_bus_match_table" [drivers/bcma/bcma.ko] undefined! Caused by commit cae761b5a6bd ("bcma: populate bus DT subnodes as platform_device-s") I have used

linux-next: build failure after merge of the wireless-drivers-next tree

Hi Kalle, After merging the wireless-drivers-next tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: of_default_bus_match_table [drivers/bcma/bcma.ko] undefined! Caused by commit cae761b5a6bd (bcma: populate bus DT subnodes as platform_device-s) I have used the

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

Hi Arend, On Wed, 27 May 2015 11:08:35 +0200 Arend van Spriel wrote: > > On 05/27/15 04:03, Stephen Rothwell wrote: > > > > After merging the wireless-drivers-next tree, today's linux-next build > > (arm multi_v7_defconfig) failed like this: > > > >

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

On 05/27/15 04:03, Stephen Rothwell wrote: Hi Kalle, After merging the wireless-drivers-next tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/net/wireless/brcm80211/brcmfmac/bcmsdh.c: In function 'brcmf_ops_sdio_probe':

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

On 05/27/15 04:03, Stephen Rothwell wrote: Hi Kalle, After merging the wireless-drivers-next tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/net/wireless/brcm80211/brcmfmac/bcmsdh.c: In function 'brcmf_ops_sdio_probe':

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

Hi Arend, On Wed, 27 May 2015 11:08:35 +0200 Arend van Spriel ar...@broadcom.com wrote: On 05/27/15 04:03, Stephen Rothwell wrote: After merging the wireless-drivers-next tree, today's linux-next build (arm multi_v7_defconfig) failed like this:

linux-next: build failure after merge of the wireless-drivers-next tree

Hi Kalle, After merging the wireless-drivers-next tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/net/wireless/brcm80211/brcmfmac/bcmsdh.c: In function 'brcmf_ops_sdio_probe': drivers/net/wireless/brcm80211/brcmfmac/bcmsdh.c:1139:7: error: dereferencing

linux-next: build failure after merge of the wireless-drivers-next tree

Hi Kalle, After merging the wireless-drivers-next tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/net/wireless/brcm80211/brcmfmac/bcmsdh.c: In function 'brcmf_ops_sdio_probe': drivers/net/wireless/brcm80211/brcmfmac/bcmsdh.c:1139:7: error: dereferencing

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

Stephen Rothwell writes: > After merging the wireless-drivers-next tree, today's linux-next build > (powerpc allyesconfig) failed like this: > > drivers/net/wireless/ath/ath9k/ath9k_htc.o:(.data+0x29d0): multiple > definition of `led_blink' >

linux-next: build failure after merge of the wireless-drivers-next tree

Hi Kalle, After merging the wireless-drivers-next tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/net/wireless/ath/ath9k/ath9k_htc.o:(.data+0x29d0): multiple definition of `led_blink' drivers/net/wireless/ath/ath9k/ath9k.o:(.bss+0x1654): first defined here

linux-next: build failure after merge of the wireless-drivers-next tree

Hi Kalle, After merging the wireless-drivers-next tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/net/wireless/ath/ath9k/ath9k_htc.o:(.data+0x29d0): multiple definition of `led_blink' drivers/net/wireless/ath/ath9k/ath9k.o:(.bss+0x1654): first defined here

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

Stephen Rothwell s...@canb.auug.org.au writes: After merging the wireless-drivers-next tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/net/wireless/ath/ath9k/ath9k_htc.o:(.data+0x29d0): multiple definition of `led_blink'