[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100508151001.GB2383@linux.vnet.ibm.com>
Date: Sat, 8 May 2010 08:10:01 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
a.p.zijlstra@...llo.nl, tglx@...utronix.de
Subject: Re: [GIT RFC PULL] RCU changes for 2.6.35
On Sat, May 08, 2010 at 10:34:21AM +0200, Ingo Molnar wrote:
>
> * Paul E. McKenney <paulmck@...ux.vnet.ibm.com> wrote:
>
> > Hello, Ingo,
> >
> > Here is the first installment of RCU changes for 2.6.35. These commits
> > are based on top of the rcu/urgent set sent yesterday. If you would rather
> > rcu/urgent be merged into tip/core/rcu and then this set based on top of
> > that, or some other arrangement, please let me know.
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git rcu/next
>
> FYI, it doesnt build on x86 allyesconfig:
>
> In file included from kernel/rcutree.c:1961:
> kernel/rcutree_plugin.h: In function ?rcu_needs_cpu?:
> kernel/rcutree_plugin.h:1066: error: invalid type argument of ?->? (have ?struct rcu_dynticks?)
> kernel/rcutree_plugin.h:1067: error: invalid type argument of ?->? (have ?struct rcu_dynticks?)
<red face>
I forgot to move CONFIG_RCU_FAST_NO_HZ from my development tests to my
regression tests. I have done so now. I have also added allyesconfig
to my compile tests, which I should have done long ago.
I am testing the fix, and will rebase the stack onto 2.6.34-rc7 when it
comes out.
Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists