From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
rmk+kernel@arm.linux.org.uk, weber@corscience.de
Subject: [GIT PULL rcu/next] 2.6.38 fixes for RCU regressions
Date: Fri, 14 Jan 2011 05:46:20 -0800 [thread overview]
Message-ID: <20110114134620.GA12672@linux.vnet.ibm.com> (raw)
Hello, Ingo,
This pull request fixes a pair of RCU regressions introduced into 2.6.38.
These changes are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git rcu/next
These are against the current tip/core/rcu branch.
Thanx, Paul
------------------>
Paul E. McKenney (2):
rcu: demote SRCU_SYNCHRONIZE_DELAY from kernel-parameter status
rcu: avoid pointless blocked-task warnings
init/Kconfig | 15 ---------------
kernel/rcutiny.c | 3 ++-
kernel/srcu.c | 15 +++++++++++++--
3 files changed, 15 insertions(+), 18 deletions(-)
next reply other threads:[~2011-01-14 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 13:46 Paul E. McKenney [this message]
2011-01-14 14:30 ` [GIT PULL rcu/next] 2.6.38 fixes for RCU regressions 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=20110114134620.GA12672@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=torvalds@linux-foundation.org \
--cc=weber@corscience.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