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] Fixes for lockdep and out-of-tree-module build problem
Date: Wed, 11 May 2011 13:59:15 -0700 [thread overview]
Message-ID: <20110511205915.GA1731@linux.vnet.ibm.com> (raw)
Hello!
These patches fix some bugs found in -tip testing:
1. Avoid a build error for some compiler arguments for out-of-tree
modules.
2. Add a generic atomic_or().
3. Use atomic_or() to avoid a lockdep splat.
Following this will be specific atomic_or() implementations for a couple
of architectures.
Thanx, Paul
------------------------------------------------------------------------
include/linux/atomic.h | 13 +++++++++++++
include/linux/rcupdate.h | 5 +++--
kernel/rcutree.c | 13 +++++--------
kernel/rcutree.h | 4 +++-
4 files changed, 24 insertions(+), 11 deletions(-)
next reply other threads:[~2011-05-11 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 20:59 Paul E. McKenney [this message]
2011-05-11 20:59 ` [PATCH tip/core/rcu 1/3] rcu: avoid build error for third-party modules Paul E. McKenney
2011-05-11 20:59 ` [PATCH tip/core/rcu 2/3] atomic: add atomic_or() Paul E. McKenney
2011-05-11 20:59 ` [PATCH tip/core/rcu 3/3] rcu: Avoid acquiring rcu_node locks in timer functions Paul E. McKenney
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=20110511205915.GA1731@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.