From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca,
josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de,
peterz@infradead.org, rostedt@goodmis.org,
Valdis.Kletnieks@vt.edu, dhowells@redhat.com,
eric.dumazet@gmail.com, darren@dvhart.com, patches@linaro.org
Subject: [PATCH tip/core/rcu 0/3] Additional RCU commits for 3.3
Date: Mon, 9 Jan 2012 14:14:57 -0800 [thread overview]
Message-ID: <20120109221457.GA28184@linux.vnet.ibm.com> (raw)
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(-)
next reply other threads:[~2012-01-09 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 22:14 Paul E. McKenney [this message]
2012-01-10 8:59 ` [PATCH tip/core/rcu 0/3] Additional RCU commits for 3.3 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=20120109221457.GA28184@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=darren@dvhart.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=eric.dumazet@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=patches@linaro.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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;
as well as URLs for NNTP newsgroup(s).