[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120109221457.GA28184@linux.vnet.ibm.com>
Date: Mon, 9 Jan 2012 14:14:57 -0800
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: linux-kernel@...r.kernel.org
Cc: mingo@...e.hu, laijs@...fujitsu.com, dipankar@...ibm.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...ymtl.ca,
josh@...htriplett.org, niv@...ibm.com, tglx@...utronix.de,
peterz@...radead.org, rostedt@...dmis.org, Valdis.Kletnieks@...edu,
dhowells@...hat.com, eric.dumazet@...il.com, darren@...art.com,
patches@...aro.org
Subject: [PATCH tip/core/rcu 0/3] Additional RCU commits for 3.3
Hello, Ingo,
Further -next and other testing uncovered one upcoming change and some
build warnings. The three commits below address these. I am putting
them forward for 3.3, but of course if the risk of change exceeds the
magnitude of the problems, I can keep them queued for 3.4. These are
all quite small, have been exposed to -next testing, and I retested them
against current tip/master.
The specific changes are as follows:
1. Change rcutorture's module parameters of type int to instead
be bool. This is in preparation for Rusty's patch that makes
type-int module parameters illegal. (Courtesy of Rusty Russell.)
2. Add "const" to the new is_idle_task()'s argument, which
addresses a build warning located by Stephen Rothwell.
3. Add __cpuinit to rcu_torture_onoff() to address a section
mismatch build warning. (Courtesy of Heiko Carstens.)
These changes are based off of 3.2-rc7 and are available in the git
repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/urgent
Thanx, Paul
------------------>
Heiko Carstens (1):
rcu: Add missing __cpuinit annotation in rcutorture code
Paul E. McKenney (1):
sched: Add "const" to is_idle_task() parameter
Rusty Russell (1):
rcu: Make rcutorture bool parameters really bool (core code)
include/linux/sched.h | 2 +-
kernel/rcutorture.c | 8 ++++----
2 files changed, 5 insertions(+), 5 deletions(-)
--
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