[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190812161236.21defb17@canb.auug.org.au>
Date: Mon, 12 Aug 2019 16:12:36 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: linux-next: build failure after merge of the rcu tree
Hi all,
After merging the rcu tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
arch/x86/xen/smp_pv.c: In function 'xen_pv_play_dead':
arch/x86/xen/smp_pv.c:439:2: error: implicit declaration of function 'tick_nohz_idle_stop_tick_protected'; did you mean 'tick_nohz_idle_stop_tick'? [-Werror=implicit-function-declaration]
tick_nohz_idle_stop_tick_protected();
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tick_nohz_idle_stop_tick
Caused by commit
a96f9dca9820 ("idle: Prevent late-arriving interrupts from disrupting offline")
Also:
In file included from <command-line>:
include/linux/rcu_segcblist.h:69:2: error: unknown type name 'atomic_long_t'
atomic_long_t len;
^~~~~~~~~~~~~
include/linux/rcu_segcblist.h:74:2: error: unknown type name 'u8'
u8 enabled;
^~
include/linux/rcu_segcblist.h:75:2: error: unknown type name 'u8'
u8 offloaded;
^~
Caused by commits:
e084617762b7 ("rcu/nocb: Use separate flag to indicate disabled ->cblist")
5e114ba3d7a5 ("rcu/nocb: Use separate flag to indicate offloaded ->cblist")
9f3ca0945104 ("rcu/nocb: Atomic ->len field in rcu_segcblist structure")
We prefer our include files to be standalone now if at all possible.
I have used the rcu tree from next-20190809 for today.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists