From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com,
bobby.prani@gmail.com
Subject: [PATCH tip/core/rcu 0/3] Documentation updates for 4.2
Date: Tue, 12 May 2015 14:22:34 -0700 [thread overview]
Message-ID: <20150512212234.GA32351@linux.vnet.ibm.com> (raw)
Hello!
This series provides a few documentation updates:
1. Fix description of smp_mb__before_spinlock() semantics, courtesy
of Will Deacon.
2. Add another caveat to the list regarding the care and feeding
of pointers returned by rcu_derefence(). You cannot let the
compiler know too much.
3. Explicitly state that each instance of rcu_dereference() will
reload the pointer, courtesy of Milos Vyletel.
Thanx, Paul
------------------------------------------------------------------------
b/Documentation/RCU/rcu_dereference.txt | 5 +++++
b/Documentation/RCU/whatisRCU.txt | 4 +++-
b/Documentation/memory-barriers.txt | 7 +++----
b/include/linux/spinlock.h | 2 +-
4 files changed, 12 insertions(+), 6 deletions(-)
next reply other threads:[~2015-05-12 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 21:22 Paul E. McKenney [this message]
2015-05-12 21:23 ` [PATCH tip/core/rcu 1/3] documentation: memory-barriers: Fix smp_mb__before_spinlock() semantics Paul E. McKenney
2015-05-12 21:23 ` [PATCH tip/core/rcu 2/3] documentation: Update rcu_dereference.txt based on WG21 discussions Paul E. McKenney
2015-05-13 18:33 ` Mathieu Desnoyers
2015-05-14 20:57 ` Paul E. McKenney
2015-05-12 21:23 ` [PATCH tip/core/rcu 3/3] documentation: State that rcu_dereference() reloads pointer 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=20150512212234.GA32351@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--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.