From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
a.p.zijlstra@chello.nl, tglx@linutronix.de
Subject: Re: [GIT RFC PULL] RCU changes for 2.6.35
Date: Sat, 8 May 2010 08:10:01 -0700 [thread overview]
Message-ID: <20100508151001.GB2383@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100508083421.GA11245@elte.hu>
On Sat, May 08, 2010 at 10:34:21AM +0200, Ingo Molnar wrote:
>
> * Paul E. McKenney <paulmck@linux.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
next prev parent reply other threads:[~2010-05-08 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 21:22 [GIT RFC PULL] RCU changes for 2.6.35 Paul E. McKenney
2010-05-08 8:34 ` Ingo Molnar
2010-05-08 15:10 ` Paul E. McKenney [this message]
2010-05-08 16:10 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100508151001.GB2383@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox