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

On Mon, May 02, 2016 at 02:37:36PM +1000, Stephen Rothwell wrote: > Hi Paul, > > After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > arch/x86/kvm/vmx.c: In function 'vmx_init': > arch/x86/kvm/vmx.c:11026:2: error: function '_r_a_p__v' is initialized

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

Hi Paul, After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) failed like this: arch/x86/kvm/vmx.c: In function 'vmx_init': arch/x86/kvm/vmx.c:11026:2: error: function '_r_a_p__v' is initialized like a variable rcu_assign_pointer(crash_vmclear_loaded_vmcss, ^ In file

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

Hi Paul, After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) failed like this: arch/x86/kvm/vmx.c: In function 'vmx_init': arch/x86/kvm/vmx.c:11026:2: error: function '_r_a_p__v' is initialized like a variable rcu_assign_pointer(crash_vmclear_loaded_vmcss, ^ In file

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

On Mon, Feb 01, 2016 at 01:55:51PM +1100, Stephen Rothwell wrote: > Hi Paul, > > After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > In file included from /home/sfr/next/next/include/linux/spinlock_types.h:18:0, > from

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

On Mon, Feb 01, 2016 at 01:55:51PM +1100, Stephen Rothwell wrote: > Hi Paul, > > After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > In file included from /home/sfr/next/next/include/linux/spinlock_types.h:18:0, > from

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

Hi Paul, After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from /home/sfr/next/next/include/linux/spinlock_types.h:18:0, from /home/sfr/next/next/include/linux/spinlock.h:81, from

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

Hi Paul, After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from /home/sfr/next/next/include/linux/spinlock_types.h:18:0, from /home/sfr/next/next/include/linux/spinlock.h:81, from

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

On Wed, Sep 02, 2015 at 09:29:18AM +0200, Ingo Molnar wrote: > > * Paul E. McKenney wrote: > > > On Tue, Sep 01, 2015 at 11:40:51PM -0700, Davidlohr Bueso wrote: > > > On Tue, 2015-09-01 at 22:26 -0700, Paul E. McKenney wrote: > > > > Davidlohr, the error is due to sched_setscheduler_nocheck()

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

* Paul E. McKenney wrote: > On Tue, Sep 01, 2015 at 11:40:51PM -0700, Davidlohr Bueso wrote: > > On Tue, 2015-09-01 at 22:26 -0700, Paul E. McKenney wrote: > > > Davidlohr, the error is due to sched_setscheduler_nocheck() not being > > > exported, so that Stephen gets this failure when building

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

On Tue, Sep 01, 2015 at 11:40:51PM -0700, Davidlohr Bueso wrote: > On Tue, 2015-09-01 at 22:26 -0700, Paul E. McKenney wrote: > > Davidlohr, the error is due to sched_setscheduler_nocheck() not being > > exported, so that Stephen gets this failure when building modules. > > This is 04be76a9b067

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

On Tue, 2015-09-01 at 22:26 -0700, Paul E. McKenney wrote: > Davidlohr, the error is due to sched_setscheduler_nocheck() not being > exported, so that Stephen gets this failure when building modules. > This is 04be76a9b067 (locktorture: Support rtmutex torturing) in -rcu. > > Thoughts? Right,

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

On Tue, 2015-09-01 at 22:26 -0700, Paul E. McKenney wrote: > Davidlohr, the error is due to sched_setscheduler_nocheck() not being > exported, so that Stephen gets this failure when building modules. > This is 04be76a9b067 (locktorture: Support rtmutex torturing) in -rcu. > > Thoughts? Right,

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

* Paul E. McKenney wrote: > On Tue, Sep 01, 2015 at 11:40:51PM -0700, Davidlohr Bueso wrote: > > On Tue, 2015-09-01 at 22:26 -0700, Paul E. McKenney wrote: > > > Davidlohr, the error is due to sched_setscheduler_nocheck() not being > > > exported, so that Stephen

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

On Wed, Sep 02, 2015 at 09:29:18AM +0200, Ingo Molnar wrote: > > * Paul E. McKenney wrote: > > > On Tue, Sep 01, 2015 at 11:40:51PM -0700, Davidlohr Bueso wrote: > > > On Tue, 2015-09-01 at 22:26 -0700, Paul E. McKenney wrote: > > > > Davidlohr, the error is due to

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

On Tue, Sep 01, 2015 at 11:40:51PM -0700, Davidlohr Bueso wrote: > On Tue, 2015-09-01 at 22:26 -0700, Paul E. McKenney wrote: > > Davidlohr, the error is due to sched_setscheduler_nocheck() not being > > exported, so that Stephen gets this failure when building modules. > > This is 04be76a9b067

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

On Wed, Sep 02, 2015 at 01:58:00PM +1000, Stephen Rothwell wrote: > Hi Paul, > > On Tue, 1 Sep 2015 00:49:46 -0700 "Paul E. McKenney" > wrote: > > > > On Tue, Sep 01, 2015 at 01:50:06PM +1000, Stephen Rothwell wrote: > > > > > > After merging the rcu tree, today's linux-next build (x86_64

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

Hi Paul, On Tue, 1 Sep 2015 00:49:46 -0700 "Paul E. McKenney" wrote: > > On Tue, Sep 01, 2015 at 01:50:06PM +1000, Stephen Rothwell wrote: > > > > After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > ERROR: "sched_setscheduler_nocheck"

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

On Tue, Sep 01, 2015 at 01:50:06PM +1000, Stephen Rothwell wrote: > Hi Paul, > > After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > ERROR: "sched_setscheduler_nocheck" [kernel/locking/locktorture.ko] undefined! > ERROR: "percpu_down_write"

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

On Tue, Sep 01, 2015 at 01:50:06PM +1000, Stephen Rothwell wrote: > Hi Paul, > > After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > ERROR: "sched_setscheduler_nocheck" [kernel/locking/locktorture.ko] undefined! > ERROR: "percpu_down_write"

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

On Wed, Sep 02, 2015 at 01:58:00PM +1000, Stephen Rothwell wrote: > Hi Paul, > > On Tue, 1 Sep 2015 00:49:46 -0700 "Paul E. McKenney" > wrote: > > > > On Tue, Sep 01, 2015 at 01:50:06PM +1000, Stephen Rothwell wrote: > > > > > > After merging the rcu tree, today's

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

Hi Paul, On Tue, 1 Sep 2015 00:49:46 -0700 "Paul E. McKenney" wrote: > > On Tue, Sep 01, 2015 at 01:50:06PM +1000, Stephen Rothwell wrote: > > > > After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > ERROR:

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

Hi Paul, After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "sched_setscheduler_nocheck" [kernel/locking/locktorture.ko] undefined! ERROR: "percpu_down_write" [kernel/locking/locktorture.ko] undefined! ERROR: "percpu_up_write"

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

Hi Paul, After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "sched_setscheduler_nocheck" [kernel/locking/locktorture.ko] undefined! ERROR: "percpu_down_write" [kernel/locking/locktorture.ko] undefined! ERROR: "percpu_up_write"

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

* Paul E. McKenney wrote: > On Fri, Jul 17, 2015 at 09:51:31PM +0200, Ingo Molnar wrote: > > > > * Paul E. McKenney wrote: > > > > > And here is a prototype patch, which I intend to merge with the existing > > > patch > > > that renames rcu_lockdep_assert() to RCU_LOCKDEP_WARN(). I will

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

On Fri, Jul 17, 2015 at 09:51:31PM +0200, Ingo Molnar wrote: > > * Paul E. McKenney wrote: > > > And here is a prototype patch, which I intend to merge with the existing > > patch > > that renames rcu_lockdep_assert() to RCU_LOCKDEP_WARN(). I will also queue > > a > > revert of the patch

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

* Paul E. McKenney wrote: > And here is a prototype patch, which I intend to merge with the existing > patch > that renames rcu_lockdep_assert() to RCU_LOCKDEP_WARN(). I will also queue a > revert of the patch below for 4.4. > > Thoughts? > >

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

On Fri, Jul 17, 2015 at 10:35:28AM -0700, Paul E. McKenney wrote: > On Fri, Jul 17, 2015 at 01:40:46PM +0200, Ingo Molnar wrote: > > > > * Paul E. McKenney wrote: > > > > > On Thu, Jul 16, 2015 at 01:14:23PM +1000, Stephen Rothwell wrote: > > > > Hi Paul, > > > > > > > > After merging the rcu

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

On Fri, Jul 17, 2015 at 01:40:46PM +0200, Ingo Molnar wrote: > > * Paul E. McKenney wrote: > > > On Thu, Jul 16, 2015 at 01:14:23PM +1000, Stephen Rothwell wrote: > > > Hi Paul, > > > > > > After merging the rcu tree, today's linux-next build (arm > > > multi_v7_defconfig) failed like this: >

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

* Paul E. McKenney wrote: > On Thu, Jul 16, 2015 at 01:14:23PM +1000, Stephen Rothwell wrote: > > Hi Paul, > > > > After merging the rcu tree, today's linux-next build (arm > > multi_v7_defconfig) failed like this: > > > > kernel/notifier.c: In function 'notify_die': > >

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

* Paul E. McKenney paul...@linux.vnet.ibm.com wrote: On Thu, Jul 16, 2015 at 01:14:23PM +1000, Stephen Rothwell wrote: Hi Paul, After merging the rcu tree, today's linux-next build (arm multi_v7_defconfig) failed like this: kernel/notifier.c: In function 'notify_die':

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

On Fri, Jul 17, 2015 at 01:40:46PM +0200, Ingo Molnar wrote: * Paul E. McKenney paul...@linux.vnet.ibm.com wrote: On Thu, Jul 16, 2015 at 01:14:23PM +1000, Stephen Rothwell wrote: Hi Paul, After merging the rcu tree, today's linux-next build (arm multi_v7_defconfig) failed like

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

On Fri, Jul 17, 2015 at 10:35:28AM -0700, Paul E. McKenney wrote: On Fri, Jul 17, 2015 at 01:40:46PM +0200, Ingo Molnar wrote: * Paul E. McKenney paul...@linux.vnet.ibm.com wrote: On Thu, Jul 16, 2015 at 01:14:23PM +1000, Stephen Rothwell wrote: Hi Paul, After merging the

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

* Paul E. McKenney paul...@linux.vnet.ibm.com wrote: And here is a prototype patch, which I intend to merge with the existing patch that renames rcu_lockdep_assert() to RCU_LOCKDEP_WARN(). I will also queue a revert of the patch below for 4.4. Thoughts?

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

On Fri, Jul 17, 2015 at 09:51:31PM +0200, Ingo Molnar wrote: * Paul E. McKenney paul...@linux.vnet.ibm.com wrote: And here is a prototype patch, which I intend to merge with the existing patch that renames rcu_lockdep_assert() to RCU_LOCKDEP_WARN(). I will also queue a revert

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

* Paul E. McKenney paul...@linux.vnet.ibm.com wrote: On Fri, Jul 17, 2015 at 09:51:31PM +0200, Ingo Molnar wrote: * Paul E. McKenney paul...@linux.vnet.ibm.com wrote: And here is a prototype patch, which I intend to merge with the existing patch that renames

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

Hi Paul, On Wed, 15 Jul 2015 20:51:38 -0700 "Paul E. McKenney" wrote: > > Thank you in both cases! I suspect that more will follow, so is there > something I can do to make this easier? (Hard for me to patch stuff > that is not yet in the tree...) No, that is what I am here for. But it

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

On Thu, Jul 16, 2015 at 01:14:23PM +1000, Stephen Rothwell wrote: > Hi Paul, > > After merging the rcu tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > kernel/notifier.c: In function 'notify_die': > kernel/notifier.c:547:2: error: implicit declaration of function

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

Hi Paul, After merging the rcu tree, today's linux-next build (arm multi_v7_defconfig) failed like this: kernel/notifier.c: In function 'notify_die': kernel/notifier.c:547:2: error: implicit declaration of function 'rcu_lockdep_assert' [-Werror=implicit-function-declaration]

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

Hi Paul, After merging the rcu tree, today's linux-next build (arm multi_v7_defconfig) failed like this: kernel/notifier.c: In function 'notify_die': kernel/notifier.c:547:2: error: implicit declaration of function 'rcu_lockdep_assert' [-Werror=implicit-function-declaration]

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

Hi Paul, On Wed, 15 Jul 2015 20:51:38 -0700 Paul E. McKenney paul...@linux.vnet.ibm.com wrote: Thank you in both cases! I suspect that more will follow, so is there something I can do to make this easier? (Hard for me to patch stuff that is not yet in the tree...) No, that is what I am

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

On Thu, Jul 16, 2015 at 01:14:23PM +1000, Stephen Rothwell wrote: Hi Paul, After merging the rcu tree, today's linux-next build (arm multi_v7_defconfig) failed like this: kernel/notifier.c: In function 'notify_die': kernel/notifier.c:547:2: error: implicit declaration of function

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

On Mon, Apr 13, 2015 at 01:34:05PM +0200, Ingo Molnar wrote: > > * Borislav Petkov wrote: > > > On Mon, Apr 13, 2015 at 08:39:17PM +1000, Stephen Rothwell wrote: > > > Hi Paul, > > > > > > After merging the rcu tree, today's linux-next build (powerpc allnoconfig) > > > failed like this: > > >

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

* Borislav Petkov wrote: > On Mon, Apr 13, 2015 at 08:39:17PM +1000, Stephen Rothwell wrote: > > Hi Paul, > > > > After merging the rcu tree, today's linux-next build (powerpc allnoconfig) > > failed like this: > > > > init/main.c: In function 'rest_init': > > init/main.c:387:2: error:

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

On Mon, Apr 13, 2015 at 08:39:17PM +1000, Stephen Rothwell wrote: > Hi Paul, > > After merging the rcu tree, today's linux-next build (powerpc allnoconfig) > failed like this: > > init/main.c: In function 'rest_init': > init/main.c:387:2: error: implicit declaration of function >

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

Hi Paul, After merging the rcu tree, today's linux-next build (powerpc allnoconfig) failed like this: init/main.c: In function 'rest_init': init/main.c:387:2: error: implicit declaration of function 'smpboot_thread_init' [-Werror=implicit-function-declaration] smpboot_thread_init(); ^

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

Hi Paul, After merging the rcu tree, today's linux-next build (powerpc allnoconfig) failed like this: init/main.c: In function 'rest_init': init/main.c:387:2: error: implicit declaration of function 'smpboot_thread_init' [-Werror=implicit-function-declaration] smpboot_thread_init(); ^

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

On Mon, Apr 13, 2015 at 08:39:17PM +1000, Stephen Rothwell wrote: Hi Paul, After merging the rcu tree, today's linux-next build (powerpc allnoconfig) failed like this: init/main.c: In function 'rest_init': init/main.c:387:2: error: implicit declaration of function 'smpboot_thread_init'

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

* Borislav Petkov b...@suse.de wrote: On Mon, Apr 13, 2015 at 08:39:17PM +1000, Stephen Rothwell wrote: Hi Paul, After merging the rcu tree, today's linux-next build (powerpc allnoconfig) failed like this: init/main.c: In function 'rest_init': init/main.c:387:2: error: implicit

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

On Mon, Apr 13, 2015 at 01:34:05PM +0200, Ingo Molnar wrote: * Borislav Petkov b...@suse.de wrote: On Mon, Apr 13, 2015 at 08:39:17PM +1000, Stephen Rothwell wrote: Hi Paul, After merging the rcu tree, today's linux-next build (powerpc allnoconfig) failed like this:

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

On Fri, Feb 27, 2015 at 01:18:56PM +1100, Stephen Rothwell wrote: > Hi Paul, > > After merging the rcu tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > arch/x86/xen/smp.c: In function 'xen_cpu_up': > arch/x86/xen/smp.c:460:6: error: 'err' undeclared (first use in this

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

Hi Paul, After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) failed like this: arch/x86/xen/smp.c: In function 'xen_cpu_up': arch/x86/xen/smp.c:460:6: error: 'err' undeclared (first use in this function) if (err) ^ Caused by commit b92c23b083d6 ("x86: Use common

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

On Fri, Feb 27, 2015 at 01:18:56PM +1100, Stephen Rothwell wrote: Hi Paul, After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) failed like this: arch/x86/xen/smp.c: In function 'xen_cpu_up': arch/x86/xen/smp.c:460:6: error: 'err' undeclared (first use in this

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

Hi Paul, After merging the rcu tree, today's linux-next build (x86_64 allmodconfig) failed like this: arch/x86/xen/smp.c: In function 'xen_cpu_up': arch/x86/xen/smp.c:460:6: error: 'err' undeclared (first use in this function) if (err) ^ Caused by commit b92c23b083d6 (x86: Use common

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

On Sat, Dec 27, 2014 at 12:20:50PM -0500, Pranith Kumar wrote: > On Sat, Dec 27, 2014 at 11:24 AM, Pranith Kumar wrote: > > On Fri, Dec 26, 2014 at 11:54 AM, Paul E. McKenney wrote: > >> Pranith, if Stephen has CONFIG_KVM=n, it might be best to move the > >> "select SRCU" to "config PPC" in

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

On Sat, Dec 27, 2014 at 12:20:50PM -0500, Pranith Kumar wrote: On Sat, Dec 27, 2014 at 11:24 AM, Pranith Kumar bobby.pr...@gmail.com wrote: On Fri, Dec 26, 2014 at 11:54 AM, Paul E. McKenney wrote: Pranith, if Stephen has CONFIG_KVM=n, it might be best to move the select SRCU to config PPC

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

On Sat, Dec 27, 2014 at 11:24 AM, Pranith Kumar wrote: > On Fri, Dec 26, 2014 at 11:54 AM, Paul E. McKenney wrote: >> Pranith, if Stephen has CONFIG_KVM=n, it might be best to move the >> "select SRCU" to "config PPC" in arch/powerpc/Kconfig. Are you able >> to cross-build powerpc? >> > > ppc 32

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

On Fri, Dec 26, 2014 at 11:54 AM, Paul E. McKenney wrote: > Pranith, if Stephen has CONFIG_KVM=n, it might be best to move the > "select SRCU" to "config PPC" in arch/powerpc/Kconfig. Are you able > to cross-build powerpc? > ppc 32 seems fine without selecting srcu unconditionally. So I added

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

On Fri, Dec 26, 2014 at 06:51:20PM +1100, Stephen Rothwell wrote: > Hi Paul, > > After merging the rcu tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > In file included from arch/powerpc/include/asm/kvm_ppc.h:30:0, > from

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

On Fri, Dec 26, 2014 at 06:51:20PM +1100, Stephen Rothwell wrote: Hi Paul, After merging the rcu tree, today's linux-next build (powerpc allyesconfig) failed like this: In file included from arch/powerpc/include/asm/kvm_ppc.h:30:0, from arch/powerpc/kernel/setup_64.c:68:

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

On Fri, Dec 26, 2014 at 11:54 AM, Paul E. McKenney wrote: Pranith, if Stephen has CONFIG_KVM=n, it might be best to move the select SRCU to config PPC in arch/powerpc/Kconfig. Are you able to cross-build powerpc? ppc 32 seems fine without selecting srcu unconditionally. So I added this

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

On Sat, Dec 27, 2014 at 11:24 AM, Pranith Kumar bobby.pr...@gmail.com wrote: On Fri, Dec 26, 2014 at 11:54 AM, Paul E. McKenney wrote: Pranith, if Stephen has CONFIG_KVM=n, it might be best to move the select SRCU to config PPC in arch/powerpc/Kconfig. Are you able to cross-build powerpc?

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

Hi Paul, After merging the rcu tree, today's linux-next build (powerpc allyesconfig) failed like this: In file included from arch/powerpc/include/asm/kvm_ppc.h:30:0, from arch/powerpc/kernel/setup_64.c:68: include/linux/kvm_host.h:366:21: error: field 'srcu' has incomplete type

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

Hi Paul, After merging the rcu tree, today's linux-next build (powerpc allyesconfig) failed like this: In file included from arch/powerpc/include/asm/kvm_ppc.h:30:0, from arch/powerpc/kernel/setup_64.c:68: include/linux/kvm_host.h:366:21: error: field 'srcu' has incomplete type

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

On Fri, Dec 12, 2014 at 05:12:15PM +1100, Stephen Rothwell wrote: > Hi Paul, > > After merging the rcu tree, today's linux-next build (powerpc64 > allnoconfig) failed like this: > > In file included from arch/powerpc/include/asm/kvm_ppc.h:30:0, > from

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

On Fri, Dec 12, 2014 at 05:12:15PM +1100, Stephen Rothwell wrote: Hi Paul, After merging the rcu tree, today's linux-next build (powerpc64 allnoconfig) failed like this: In file included from arch/powerpc/include/asm/kvm_ppc.h:30:0, from arch/powerpc/kernel/setup_64.c:68:

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

Hi Paul, After merging the rcu tree, today's linux-next build (powerpc64 allnoconfig) failed like this: In file included from arch/powerpc/include/asm/kvm_ppc.h:30:0, from arch/powerpc/kernel/setup_64.c:68: include/linux/kvm_host.h:366:21: error: field 'srcu' has incomplete type

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

Hi Paul, After merging the rcu tree, today's linux-next build (powerpc64 allnoconfig) failed like this: In file included from arch/powerpc/include/asm/kvm_ppc.h:30:0, from arch/powerpc/kernel/setup_64.c:68: include/linux/kvm_host.h:366:21: error: field 'srcu' has incomplete type

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

On Wed, Dec 10, 2014 at 10:03:57AM -0500, Pranith Kumar wrote: > On 12/10/2014 03:09 AM, Stephen Rothwell wrote: > > Hi Paul, > > > > After merging the rcu tree, today's linux-next build (powerpc64 > > allnoconfig) failed like this: > > > > In file included from

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

On 12/10/2014 03:09 AM, Stephen Rothwell wrote: > Hi Paul, > > After merging the rcu tree, today's linux-next build (powerpc64 > allnoconfig) failed like this: > > In file included from arch/powerpc/include/asm/kvm_ppc.h:30:0, > from arch/powerpc/kernel/setup_64.c:68: >

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

Hi Paul, After merging the rcu tree, today's linux-next build (powerpc64 allnoconfig) failed like this: In file included from arch/powerpc/include/asm/kvm_ppc.h:30:0, from arch/powerpc/kernel/setup_64.c:68: include/linux/kvm_host.h:366:21: error: field 'srcu' has incomplete type

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

Hi Paul, After merging the rcu tree, today's linux-next build (powerpc64 allnoconfig) failed like this: In file included from arch/powerpc/include/asm/kvm_ppc.h:30:0, from arch/powerpc/kernel/setup_64.c:68: include/linux/kvm_host.h:366:21: error: field 'srcu' has incomplete type

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

On 12/10/2014 03:09 AM, Stephen Rothwell wrote: Hi Paul, After merging the rcu tree, today's linux-next build (powerpc64 allnoconfig) failed like this: In file included from arch/powerpc/include/asm/kvm_ppc.h:30:0, from arch/powerpc/kernel/setup_64.c:68:

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

On Wed, Dec 10, 2014 at 10:03:57AM -0500, Pranith Kumar wrote: On 12/10/2014 03:09 AM, Stephen Rothwell wrote: Hi Paul, After merging the rcu tree, today's linux-next build (powerpc64 allnoconfig) failed like this: In file included from arch/powerpc/include/asm/kvm_ppc.h:30:0,

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

On Tue, Dec 09, 2014 at 10:42:30PM +1100, Stephen Rothwell wrote: > Hi Paul, > > After merging the rcu tree, today's linux-next build (powerpc > allnoconfig) failed like this: > > include/linux/notifier.h:51:4: warning: its scope is only this definition or > declaration, which is probably not

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

Hi Paul, After merging the rcu tree, today's linux-next build (powerpc allnoconfig) failed like this: include/linux/notifier.h:51:4: warning: its scope is only this definition or declaration, which is probably not what you want In file included from include/linux/memory_hotplug.h:6:0,

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

Hi Paul, After merging the rcu tree, today's linux-next build (powerpc allnoconfig) failed like this: include/linux/notifier.h:51:4: warning: its scope is only this definition or declaration, which is probably not what you want In file included from include/linux/memory_hotplug.h:6:0,

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

On Tue, Dec 09, 2014 at 10:42:30PM +1100, Stephen Rothwell wrote: Hi Paul, After merging the rcu tree, today's linux-next build (powerpc allnoconfig) failed like this: include/linux/notifier.h:51:4: warning: its scope is only this definition or declaration, which is probably not what you

<    1   2