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

Hi Ingo, On Tue, 1 Mar 2016 08:07:50 +0100 Ingo Molnar wrote: > > > This build is done with a PowerPC hosted cross compiler with no glibc. > > Ugh, what a rare and weird way to build an x86 kernel, and you made > linux-next > dependent on it? It is just the fastest

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

Hi Ingo, On Tue, 1 Mar 2016 08:07:50 +0100 Ingo Molnar wrote: > > > This build is done with a PowerPC hosted cross compiler with no glibc. > > Ugh, what a rare and weird way to build an x86 kernel, and you made > linux-next > dependent on it? It is just the fastest hardware I currently

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

On Tue, Mar 1, 2016 at 8:39 AM, H. Peter Anvin wrote: > On February 29, 2016 11:28:22 PM PST, Sedat Dilek > wrote: >>On Tue, Mar 1, 2016 at 8:07 AM, Ingo Molnar wrote: >>> >>> * Stephen Rothwell wrote: >>> Hi

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

On Tue, Mar 1, 2016 at 8:39 AM, H. Peter Anvin wrote: > On February 29, 2016 11:28:22 PM PST, Sedat Dilek > wrote: >>On Tue, Mar 1, 2016 at 8:07 AM, Ingo Molnar wrote: >>> >>> * Stephen Rothwell wrote: >>> Hi all, After merging the tip tree, today's linux-next build (x86_64

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

On February 29, 2016 11:28:22 PM PST, Sedat Dilek wrote: >On Tue, Mar 1, 2016 at 8:07 AM, Ingo Molnar wrote: >> >> * Stephen Rothwell wrote: >> >>> Hi all, >>> >>> After merging the tip tree, today's linux-next build (x86_64

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

On February 29, 2016 11:28:22 PM PST, Sedat Dilek wrote: >On Tue, Mar 1, 2016 at 8:07 AM, Ingo Molnar wrote: >> >> * Stephen Rothwell wrote: >> >>> Hi all, >>> >>> After merging the tip tree, today's linux-next build (x86_64 >allmodconfig) >>> failed like this: >>> >>> DESCEND objtool >>>

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

On Tue, Mar 1, 2016 at 8:07 AM, Ingo Molnar wrote: > > * Stephen Rothwell wrote: > >> Hi all, >> >> After merging the tip tree, today's linux-next build (x86_64 allmodconfig) >> failed like this: >> >> DESCEND objtool >> CC

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

On Tue, Mar 1, 2016 at 8:07 AM, Ingo Molnar wrote: > > * Stephen Rothwell wrote: > >> Hi all, >> >> After merging the tip tree, today's linux-next build (x86_64 allmodconfig) >> failed like this: >> >> DESCEND objtool >> CC

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

* Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > DESCEND objtool > CC /home/sfr/next/x86_64_allmodconfig/tools/objtool/builtin-check.o > CC

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

* Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > DESCEND objtool > CC /home/sfr/next/x86_64_allmodconfig/tools/objtool/builtin-check.o > CC

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

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: DESCEND objtool CC /home/sfr/next/x86_64_allmodconfig/tools/objtool/builtin-check.o CC /home/sfr/next/x86_64_allmodconfig/tools/objtool/special.o CC

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

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: DESCEND objtool CC /home/sfr/next/x86_64_allmodconfig/tools/objtool/builtin-check.o CC /home/sfr/next/x86_64_allmodconfig/tools/objtool/special.o CC

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

Hi Jiri, On Wed, 30 Sep 2015 08:08:12 +0200 Jiri Olsa wrote: > > ouch, forgot to CC you, sry No worries, I was watching ... > it won't fix the build if you still have old .cmd file in you tree (I presume > that's the case), > once those are regenerated you shouldn't meet the issue again

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

On Wed, Sep 30, 2015 at 12:56:40PM +1000, Stephen Rothwell wrote: > Hi all, > > On Thu, 17 Sep 2015 10:34:23 +1000 Stephen Rothwell > wrote: > > > > On Wed, 16 Sep 2015 08:16:52 +0200 Jiri Olsa wrote: > > > > > > On Wed, Sep 16, 2015 at 10:12:45AM +1000, Stephen Rothwell wrote: > > > > > > >

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

On Wed, Sep 30, 2015 at 12:56:40PM +1000, Stephen Rothwell wrote: > Hi all, > > On Thu, 17 Sep 2015 10:34:23 +1000 Stephen Rothwell > wrote: > > > > On Wed, 16 Sep 2015 08:16:52 +0200 Jiri Olsa wrote: > > > > > > On Wed, Sep 16, 2015 at 10:12:45AM

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

Hi Jiri, On Wed, 30 Sep 2015 08:08:12 +0200 Jiri Olsa wrote: > > ouch, forgot to CC you, sry No worries, I was watching ... > it won't fix the build if you still have old .cmd file in you tree (I presume > that's the case), > once those are regenerated you shouldn't meet the

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

Hi all, On Thu, 17 Sep 2015 10:34:23 +1000 Stephen Rothwell wrote: > > On Wed, 16 Sep 2015 08:16:52 +0200 Jiri Olsa wrote: > > > > On Wed, Sep 16, 2015 at 10:12:45AM +1000, Stephen Rothwell wrote: > > > > > > After merging the tip tree, today's linux-next build (perf) failed > > > like this:

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

Hi all, On Thu, 17 Sep 2015 10:34:23 +1000 Stephen Rothwell wrote: > > On Wed, 16 Sep 2015 08:16:52 +0200 Jiri Olsa wrote: > > > > On Wed, Sep 16, 2015 at 10:12:45AM +1000, Stephen Rothwell wrote: > > > > > > After merging the tip tree, today's

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

Hi Jiri, On Wed, 16 Sep 2015 08:16:52 +0200 Jiri Olsa wrote: > > On Wed, Sep 16, 2015 at 10:12:45AM +1000, Stephen Rothwell wrote: > > > > After merging the tip tree, today's linux-next build (perf) failed > > like this: > > > > make[3]: *** No rule to make target 'tools/lib/api/fs/debugfs.h',

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

Em Wed, Sep 16, 2015 at 05:30:25PM +1000, Stephen Rothwell escreveu: > Hi Jiri, > > On Wed, 16 Sep 2015 08:38:17 +0200 Jiri Olsa wrote: > > > > > > Also, building perf seems to ignore O= on the make invocation. > > > > Is that expected? > > > > > > hum, not sure about this one.. I'm not using

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

Hi Jiri, On Wed, 16 Sep 2015 08:38:17 +0200 Jiri Olsa wrote: > > > > Also, building perf seems to ignore O= on the make invocation. > > > Is that expected? > > > > hum, not sure about this one.. I'm not using it, but we have > > tests for this and I thought we're ok.. I'll check > > seems to

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

On Wed, Sep 16, 2015 at 08:16:52AM +0200, Jiri Olsa wrote: > On Wed, Sep 16, 2015 at 10:12:45AM +1000, Stephen Rothwell wrote: > > Hi all, > > > > After merging the tip tree, today's linux-next build (perf) failed > > like this: > > > > make[3]: *** No rule to make target

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

On Wed, Sep 16, 2015 at 10:12:45AM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (perf) failed > like this: > > make[3]: *** No rule to make target 'tools/lib/api/fs/debugfs.h', needed by > 'tools/perf/arch/common.o'. Stop. >

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

On Wed, Sep 16, 2015 at 10:12:45AM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (perf) failed > like this: > > make[3]: *** No rule to make target 'tools/lib/api/fs/debugfs.h', needed by > 'tools/perf/arch/common.o'. Stop. >

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

On Wed, Sep 16, 2015 at 08:16:52AM +0200, Jiri Olsa wrote: > On Wed, Sep 16, 2015 at 10:12:45AM +1000, Stephen Rothwell wrote: > > Hi all, > > > > After merging the tip tree, today's linux-next build (perf) failed > > like this: > > > > make[3]: *** No rule to make target

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

Hi Jiri, On Wed, 16 Sep 2015 08:38:17 +0200 Jiri Olsa wrote: > > > > Also, building perf seems to ignore O= on the make invocation. > > > Is that expected? > > > > hum, not sure about this one.. I'm not using it, but we have > > tests for this and I thought we're ok.. I'll

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

Em Wed, Sep 16, 2015 at 05:30:25PM +1000, Stephen Rothwell escreveu: > Hi Jiri, > > On Wed, 16 Sep 2015 08:38:17 +0200 Jiri Olsa wrote: > > > > > > Also, building perf seems to ignore O= on the make invocation. > > > > Is that expected? > > > > > > hum, not sure about this

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

Hi Jiri, On Wed, 16 Sep 2015 08:16:52 +0200 Jiri Olsa wrote: > > On Wed, Sep 16, 2015 at 10:12:45AM +1000, Stephen Rothwell wrote: > > > > After merging the tip tree, today's linux-next build (perf) failed > > like this: > > > > make[3]: *** No rule to make target

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

From: Stephen Rothwell Date: Wed, 16 Sep 2015 11:30:53 +1000 > I have added the following fix patch for today: > > From: Stephen Rothwell > Date: Wed, 16 Sep 2015 11:10:16 +1000 > Subject: [PATCH] cdc: add header guards > > Signed-off-by: Stephen Rothwell Applied, thanks Stephen. -- To

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

Hi all, After merging the next-20150915 version of the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from drivers/usb/gadget/function/u_ether.h:20:0, from drivers/usb/gadget/function/f_ncm.c:26: include/linux/usb/cdc.h:23:8: error:

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

Hi all, After merging the tip tree, today's linux-next build (perf) failed like this: make[3]: *** No rule to make target 'tools/lib/api/fs/debugfs.h', needed by 'tools/perf/arch/common.o'. Stop. tools/build/Makefile.build:109: recipe for target 'arch' failed make[4]: *** No rule to make

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

From: Stephen Rothwell Date: Wed, 16 Sep 2015 11:30:53 +1000 > I have added the following fix patch for today: > > From: Stephen Rothwell > Date: Wed, 16 Sep 2015 11:10:16 +1000 > Subject: [PATCH] cdc: add header guards > > Signed-off-by: Stephen

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

Hi all, After merging the tip tree, today's linux-next build (perf) failed like this: make[3]: *** No rule to make target 'tools/lib/api/fs/debugfs.h', needed by 'tools/perf/arch/common.o'. Stop. tools/build/Makefile.build:109: recipe for target 'arch' failed make[4]: *** No rule to make

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

Hi all, After merging the next-20150915 version of the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from drivers/usb/gadget/function/u_ether.h:20:0, from drivers/usb/gadget/function/f_ncm.c:26: include/linux/usb/cdc.h:23:8: error:

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

On Tue, Jul 28, 2015 at 06:34:19PM +0200, Luis R. Rodriguez wrote: > On Tue, Jul 28, 2015 at 03:33:03PM +1000, Stephen Rothwell wrote: > > Hi all, > > > > After merging the tip tree, today's linux-next build (powerpc > > allyesconfig) failed like this: > > > >

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

On Tue, Jul 28, 2015 at 03:33:03PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > drivers/video/fbdev/aty/atyfb_base.c: In function 'atyfb_setup_generic': >

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

Hi Sudeep, Stephen, On 28/07/2015 10:41, Sudeep Holla wrote: > Hi Stephen, > > On 28/07/15 03:43, Stephen Rothwell wrote: >> Hi all, >> >> After merging the tip tree, today's linux-next build (arm >> multi_v7_defconfig) failed like this: >> >> arch/arm/mach-mvebu/board-v7.c: In function

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

Hi Stephen, On 28/07/15 03:43, Stephen Rothwell wrote: Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/mach-mvebu/board-v7.c: In function 'mvebu_init_irq': arch/arm/mach-mvebu/board-v7.c:138:3: error: implicit declaration of

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

Hi Stephen, On 28/07/15 03:43, Stephen Rothwell wrote: Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/mach-mvebu/board-v7.c: In function 'mvebu_init_irq': arch/arm/mach-mvebu/board-v7.c:138:3: error: implicit declaration of

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

Hi Sudeep, Stephen, On 28/07/2015 10:41, Sudeep Holla wrote: Hi Stephen, On 28/07/15 03:43, Stephen Rothwell wrote: Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/mach-mvebu/board-v7.c: In function 'mvebu_init_irq':

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

On Tue, Jul 28, 2015 at 03:33:03PM +1000, Stephen Rothwell wrote: Hi all, After merging the tip tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/video/fbdev/aty/atyfb_base.c: In function 'atyfb_setup_generic': drivers/video/fbdev/aty/atyfb_base.c:3447:2:

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

On Tue, Jul 28, 2015 at 06:34:19PM +0200, Luis R. Rodriguez wrote: On Tue, Jul 28, 2015 at 03:33:03PM +1000, Stephen Rothwell wrote: Hi all, After merging the tip tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/video/fbdev/aty/atyfb_base.c: In

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

Hi all, After merging the tip tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/video/fbdev/aty/atyfb_base.c: In function 'atyfb_setup_generic': drivers/video/fbdev/aty/atyfb_base.c:3447:2: error: implicit declaration of function 'ioremap_uc'

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

Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/mach-mvebu/board-v7.c: In function 'mvebu_init_irq': arch/arm/mach-mvebu/board-v7.c:138:3: error: implicit declaration of function 'gic_set_irqchip_flags'

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

Hi all, After merging the tip tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/video/fbdev/aty/atyfb_base.c: In function 'atyfb_setup_generic': drivers/video/fbdev/aty/atyfb_base.c:3447:2: error: implicit declaration of function 'ioremap_uc'

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

Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/mach-mvebu/board-v7.c: In function 'mvebu_init_irq': arch/arm/mach-mvebu/board-v7.c:138:3: error: implicit declaration of function 'gic_set_irqchip_flags'

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

Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/pinctrl/sirf/pinctrl-atlas7.c: In function 'atlas7_gpio_handle_irq': drivers/pinctrl/sirf/pinctrl-atlas7.c:4300:20: error: 'irq' undeclared (first use in this function) if

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

Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/pinctrl/sirf/pinctrl-atlas7.c: In function 'atlas7_gpio_handle_irq': drivers/pinctrl/sirf/pinctrl-atlas7.c:4300:20: error: 'irq' undeclared (first use in this function) if

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

On Wed, 8 Jul 2015, Stephen Rothwell wrote: > After merging the tip tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > kernel/cpu.c: In function '_cpu_down': > kernel/cpu.c:398:2: error: implicit declaration of function 'irq_lock_sparse' >

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

On Wed, 8 Jul 2015, Stephen Rothwell wrote: After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: kernel/cpu.c: In function '_cpu_down': kernel/cpu.c:398:2: error: implicit declaration of function 'irq_lock_sparse'

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

Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: kernel/cpu.c: In function '_cpu_down': kernel/cpu.c:398:2: error: implicit declaration of function 'irq_lock_sparse' [-Werror=implicit-function-declaration] irq_lock_sparse(); ^

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

Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: kernel/cpu.c: In function '_cpu_down': kernel/cpu.c:398:2: error: implicit declaration of function 'irq_lock_sparse' [-Werror=implicit-function-declaration] irq_lock_sparse(); ^

RE: linux-next: build failure after merge of the tip tree

> -Original Message- > From: David Miller [mailto:da...@davemloft.net] > ... > > Thanks. Much appreciated. > > This doesn't work, neither of these emails are a formal proper submission > of a fix for this build failure. > > One of you has to do the work to formally submit the patch to

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

; David >> S.Miller >> Cc: linux-n...@vger.kernel.org; linux-kernel@vger.kernel.org; >> s...@canb.auug.org.au; Chickles, Derek; Burla, Satananda; Manlunas, Felix; >> Richter, Robert; Makarov, Aleksey; Vatsavayi, Raghu >> Subject: linux-next: build failure after merge of the ti

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

Hi all, After merging the tip tree, today's linux-next build (x86_allmodconfig) failed like this: drivers/net/ethernet/cavium/liquidio/request_manager.c: In function 'octeon_init_instr_queue': drivers/net/ethernet/cavium/liquidio/request_manager.c:111:2: error: implicit declaration of

RE: linux-next: build failure after merge of the tip tree

-Original Message- From: David Miller [mailto:da...@davemloft.net] ... Thanks. Much appreciated. This doesn't work, neither of these emails are a formal proper submission of a fix for this build failure. One of you has to do the work to formally submit the patch to netdev

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

Cc: linux-n...@vger.kernel.org; linux-kernel@vger.kernel.org; s...@canb.auug.org.au; Chickles, Derek; Burla, Satananda; Manlunas, Felix; Richter, Robert; Makarov, Aleksey; Vatsavayi, Raghu Subject: linux-next: build failure after merge of the tip tree Hi all, After merging the tip tree

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

Hi all, After merging the tip tree, today's linux-next build (x86_allmodconfig) failed like this: drivers/net/ethernet/cavium/liquidio/request_manager.c: In function 'octeon_init_instr_queue': drivers/net/ethernet/cavium/liquidio/request_manager.c:111:2: error: implicit declaration of

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

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/kernel.h:13:0, from include/linux/interrupt.h:5, from drivers/iommu/intel_irq_remapping.c:4:

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

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/kernel.h:13:0, from include/linux/interrupt.h:5, from drivers/iommu/intel_irq_remapping.c:4:

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

Hi all, On Wed, 8 Apr 2015 15:03:27 +1000 Stephen Rothwell wrote: > > Hi all, > > On Tue, 07 Apr 2015 21:54:05 +0200 Daniel Borkmann > wrote: > > > > On 04/07/2015 06:18 PM, Alexei Starovoitov wrote: > > > On 4/7/15 4:13 AM, Daniel Borkmann wrote: > > >> [ Cc'ing Dave, fyi ] > > >> > > >> On

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

Hi all, On Wed, 8 Apr 2015 15:03:27 +1000 Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, On Tue, 07 Apr 2015 21:54:05 +0200 Daniel Borkmann dan...@iogearbox.net wrote: On 04/07/2015 06:18 PM, Alexei Starovoitov wrote: On 4/7/15 4:13 AM, Daniel Borkmann wrote: [ Cc'ing

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

Hi Russell, On Mon, 30 Mar 2015 16:08:38 +0100 Russell King - ARM Linux wrote: > > On Mon, Mar 30, 2015 at 09:57:48AM -0500, Nathan Lynch wrote: > > On 03/30/2015 03:08 AM, Stephen Rothwell wrote: > > > Hi Russell, > > > > > > On Mon, 30 Mar 2015 08:15:37 +0100 Russell King - ARM Linux > > >

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

Hi Russell, On Mon, 30 Mar 2015 16:08:38 +0100 Russell King - ARM Linux li...@arm.linux.org.uk wrote: On Mon, Mar 30, 2015 at 09:57:48AM -0500, Nathan Lynch wrote: On 03/30/2015 03:08 AM, Stephen Rothwell wrote: Hi Russell, On Mon, 30 Mar 2015 08:15:37 +0100 Russell King - ARM

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

Hi all, On Tue, 07 Apr 2015 21:54:05 +0200 Daniel Borkmann wrote: > > On 04/07/2015 06:18 PM, Alexei Starovoitov wrote: > > On 4/7/15 4:13 AM, Daniel Borkmann wrote: > >> [ Cc'ing Dave, fyi ] > >> > >> On 04/07/2015 11:05 AM, Stephen Rothwell wrote: > >>> On Tue, 07 Apr 2015 10:56:13 +0200

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

On 04/07/2015 06:18 PM, Alexei Starovoitov wrote: On 4/7/15 4:13 AM, Daniel Borkmann wrote: [ Cc'ing Dave, fyi ] On 04/07/2015 11:05 AM, Stephen Rothwell wrote: On Tue, 07 Apr 2015 10:56:13 +0200 Daniel Borkmann wrote: On 04/07/2015 10:48 AM, Ingo Molnar wrote: * Stephen Rothwell wrote:

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

On 4/7/15 4:13 AM, Daniel Borkmann wrote: [ Cc'ing Dave, fyi ] On 04/07/2015 11:05 AM, Stephen Rothwell wrote: On Tue, 07 Apr 2015 10:56:13 +0200 Daniel Borkmann wrote: On 04/07/2015 10:48 AM, Ingo Molnar wrote: * Stephen Rothwell wrote: After merging the tip tree, today's linux-next

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

[ Cc'ing Dave, fyi ] On 04/07/2015 11:05 AM, Stephen Rothwell wrote: On Tue, 07 Apr 2015 10:56:13 +0200 Daniel Borkmann wrote: On 04/07/2015 10:48 AM, Ingo Molnar wrote: * Stephen Rothwell wrote: After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) failed like

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

Hi Daniel, On Tue, 07 Apr 2015 10:56:13 +0200 Daniel Borkmann wrote: > > On 04/07/2015 10:48 AM, Ingo Molnar wrote: > > > > * Stephen Rothwell wrote: > > > >> After merging the tip tree, today's linux-next build (powerpc > >> ppc64_defconfig) failed like this: > >> > >> kernel/events/core.c: In

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

On 04/07/2015 10:48 AM, Ingo Molnar wrote: * Stephen Rothwell wrote: Hi all, After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: kernel/events/core.c: In function 'perf_event_set_bpf_prog': kernel/events/core.c:6732:15: error: 'struct

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

On Tue, Apr 07, 2015 at 05:18:58PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > kernel/events/core.c: In function 'perf_event_set_bpf_prog': > kernel/events/core.c:6732:15: error: 'struct

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

* Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > kernel/events/core.c: In function 'perf_event_set_bpf_prog': > kernel/events/core.c:6732:15: error: 'struct bpf_prog_aux' has no member > named

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

Hi all, After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: kernel/events/core.c: In function 'perf_event_set_bpf_prog': kernel/events/core.c:6732:15: error: 'struct bpf_prog_aux' has no member named 'prog_type' if (prog->aux->prog_type !=

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

Hi all, After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: kernel/events/core.c: In function 'perf_event_set_bpf_prog': kernel/events/core.c:6732:15: error: 'struct bpf_prog_aux' has no member named 'prog_type' if (prog-aux-prog_type !=

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

* Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: kernel/events/core.c: In function 'perf_event_set_bpf_prog': kernel/events/core.c:6732:15: error: 'struct bpf_prog_aux' has no member

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

On Tue, Apr 07, 2015 at 05:18:58PM +1000, Stephen Rothwell wrote: Hi all, After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: kernel/events/core.c: In function 'perf_event_set_bpf_prog': kernel/events/core.c:6732:15: error: 'struct

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

Hi Daniel, On Tue, 07 Apr 2015 10:56:13 +0200 Daniel Borkmann dan...@iogearbox.net wrote: On 04/07/2015 10:48 AM, Ingo Molnar wrote: * Stephen Rothwell s...@canb.auug.org.au wrote: After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) failed like this:

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

On 04/07/2015 10:48 AM, Ingo Molnar wrote: * Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: kernel/events/core.c: In function 'perf_event_set_bpf_prog': kernel/events/core.c:6732:15:

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

[ Cc'ing Dave, fyi ] On 04/07/2015 11:05 AM, Stephen Rothwell wrote: On Tue, 07 Apr 2015 10:56:13 +0200 Daniel Borkmann dan...@iogearbox.net wrote: On 04/07/2015 10:48 AM, Ingo Molnar wrote: * Stephen Rothwell s...@canb.auug.org.au wrote: After merging the tip tree, today's linux-next build

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

On 4/7/15 4:13 AM, Daniel Borkmann wrote: [ Cc'ing Dave, fyi ] On 04/07/2015 11:05 AM, Stephen Rothwell wrote: On Tue, 07 Apr 2015 10:56:13 +0200 Daniel Borkmann dan...@iogearbox.net wrote: On 04/07/2015 10:48 AM, Ingo Molnar wrote: * Stephen Rothwell s...@canb.auug.org.au wrote: After

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

On 04/07/2015 06:18 PM, Alexei Starovoitov wrote: On 4/7/15 4:13 AM, Daniel Borkmann wrote: [ Cc'ing Dave, fyi ] On 04/07/2015 11:05 AM, Stephen Rothwell wrote: On Tue, 07 Apr 2015 10:56:13 +0200 Daniel Borkmann dan...@iogearbox.net wrote: On 04/07/2015 10:48 AM, Ingo Molnar wrote: *

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

Hi all, On Tue, 07 Apr 2015 21:54:05 +0200 Daniel Borkmann dan...@iogearbox.net wrote: On 04/07/2015 06:18 PM, Alexei Starovoitov wrote: On 4/7/15 4:13 AM, Daniel Borkmann wrote: [ Cc'ing Dave, fyi ] On 04/07/2015 11:05 AM, Stephen Rothwell wrote: On Tue, 07 Apr 2015 10:56:13 +0200

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

On 03/30/2015 10:08 AM, Russell King - ARM Linux wrote: > On Mon, Mar 30, 2015 at 09:57:48AM -0500, Nathan Lynch wrote: >> On 03/30/2015 03:08 AM, Stephen Rothwell wrote: >>> Hi Russell, >>> >>> On Mon, 30 Mar 2015 08:15:37 +0100 Russell King - ARM Linux >>> wrote: I'll drop the VDSO

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

On Mon, Mar 30, 2015 at 09:57:48AM -0500, Nathan Lynch wrote: > On 03/30/2015 03:08 AM, Stephen Rothwell wrote: > > Hi Russell, > > > > On Mon, 30 Mar 2015 08:15:37 +0100 Russell King - ARM Linux > > wrote: > >> > >> I'll drop the VDSO stuff from the ARM tree; I can't see a way to keep > >> it

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

On 03/30/2015 03:08 AM, Stephen Rothwell wrote: > Hi Russell, > > On Mon, 30 Mar 2015 08:15:37 +0100 Russell King - ARM Linux > wrote: >> >> I'll drop the VDSO stuff from the ARM tree; I can't see a way to keep >> it in my tree and keep my tree buildable without dragging in the tip >> tree. >

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

Hi Russell, On Mon, 30 Mar 2015 08:15:37 +0100 Russell King - ARM Linux wrote: > > I'll drop the VDSO stuff from the ARM tree; I can't see a way to keep > it in my tree and keep my tree buildable without dragging in the tip > tree. Does it affect your tree on its own? If not, then it can be

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

On Mon, Mar 30, 2015 at 05:13:34PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > arch/arm/kernel/vdso.c: In function 'tk_is_cntvct': > arch/arm/kernel/vdso.c:273:15: error: 'const struct

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

Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/kernel/vdso.c: In function 'tk_is_cntvct': arch/arm/kernel/vdso.c:273:15: error: 'const struct timekeeper' has no member named 'tkr' if (strcmp(tk->tkr.clock->name,

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

On Mon, Mar 30, 2015 at 05:13:34PM +1100, Stephen Rothwell wrote: Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/kernel/vdso.c: In function 'tk_is_cntvct': arch/arm/kernel/vdso.c:273:15: error: 'const struct timekeeper' has

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

Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/kernel/vdso.c: In function 'tk_is_cntvct': arch/arm/kernel/vdso.c:273:15: error: 'const struct timekeeper' has no member named 'tkr' if (strcmp(tk-tkr.clock-name, arch_sys_counter)

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

Hi Russell, On Mon, 30 Mar 2015 08:15:37 +0100 Russell King - ARM Linux li...@arm.linux.org.uk wrote: I'll drop the VDSO stuff from the ARM tree; I can't see a way to keep it in my tree and keep my tree buildable without dragging in the tip tree. Does it affect your tree on its own? If

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

On 03/30/2015 03:08 AM, Stephen Rothwell wrote: Hi Russell, On Mon, 30 Mar 2015 08:15:37 +0100 Russell King - ARM Linux li...@arm.linux.org.uk wrote: I'll drop the VDSO stuff from the ARM tree; I can't see a way to keep it in my tree and keep my tree buildable without dragging in the tip

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

On Mon, Mar 30, 2015 at 09:57:48AM -0500, Nathan Lynch wrote: On 03/30/2015 03:08 AM, Stephen Rothwell wrote: Hi Russell, On Mon, 30 Mar 2015 08:15:37 +0100 Russell King - ARM Linux li...@arm.linux.org.uk wrote: I'll drop the VDSO stuff from the ARM tree; I can't see a way to keep

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

On 03/30/2015 10:08 AM, Russell King - ARM Linux wrote: On Mon, Mar 30, 2015 at 09:57:48AM -0500, Nathan Lynch wrote: On 03/30/2015 03:08 AM, Stephen Rothwell wrote: Hi Russell, On Mon, 30 Mar 2015 08:15:37 +0100 Russell King - ARM Linux li...@arm.linux.org.uk wrote: I'll drop the VDSO

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

On 07/29/2014 04:56 PM, Stephen Rothwell wrote: > Hi all, > > On Fri, 25 Jul 2014 14:45:22 +1000 Stephen Rothwell wrote: >> >> Hi all, >> >> After merging the tip tree, today's linux-next build (powerpc >> ppc64_defconfig) failed like this: >> >> arch/powerpc/kernel/time.c:743:6: error:

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

Hi all, On Fri, 25 Jul 2014 14:45:22 +1000 Stephen Rothwell wrote: > > Hi all, > > After merging the tip tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > arch/powerpc/kernel/time.c:743:6: error: conflicting types for > 'update_vsyscall_old' > void

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

Hi all, On Fri, 25 Jul 2014 14:45:22 +1000 Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/kernel/time.c:743:6: error: conflicting types for 'update_vsyscall_old' void

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

On 07/29/2014 04:56 PM, Stephen Rothwell wrote: Hi all, On Fri, 25 Jul 2014 14:45:22 +1000 Stephen Rothwell s...@canb.auug.org.au wrote: Hi all, After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/kernel/time.c:743:6: error:

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

Hi all, After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/kernel/time.c:743:6: error: conflicting types for 'update_vsyscall_old' void update_vsyscall_old(struct timespec *wall_time, struct timespec *wtm, ^ In file included from

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

Hi all, After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/kernel/time.c:743:6: error: conflicting types for 'update_vsyscall_old' void update_vsyscall_old(struct timespec *wall_time, struct timespec *wtm, ^ In file included from

<    1   2   3   4   5   >