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, niv@us.ibm.com, 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, sbw@mit.edu
Subject: [PATCH tip/core/rcu 0/4] Documentation changes for 3.17
Date: Mon, 7 Jul 2014 15:23:45 -0700 [thread overview]
Message-ID: <20140707222345.GA6320@linux.vnet.ibm.com> (raw)
Hello!
This series provides a few documentation updates:
1. Clarify that if there is nothing awakened, then there is no
memory barrier.
2. Fix broken RTFP URL, courtesy of Pranith Kumar.
3. Add acquire/release barrier to memory-barrier pairing rules.
4. Add pointer to percpu-ref in rcuref.txt documentation.
Thanx, Paul
------------------------------------------------------------------------
b/Documentation/RCU/RTFP.txt | 4 ++--
b/Documentation/RCU/rcuref.txt | 9 +++++++++
b/Documentation/memory-barriers.txt | 25 +++++++++++++++++++++----
3 files changed, 32 insertions(+), 6 deletions(-)
next reply other threads:[~2014-07-07 22:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 22:23 Paul E. McKenney [this message]
2014-07-07 22:24 ` [PATCH tip/core/rcu 1/4] documentation: Clarify wake-up/memory-barrier relationship Paul E. McKenney
2014-07-07 22:24 ` [PATCH tip/core/rcu 2/4] documentation: Update reference, kerneltrap.org no longer works Paul E. McKenney
2014-07-07 22:24 ` [PATCH tip/core/rcu 3/4] documentation: Add acquire/release barriers to pairing rules Paul E. McKenney
2014-07-08 7:59 ` Peter Zijlstra
2014-07-08 15:31 ` Paul E. McKenney
2014-07-14 11:57 ` Peter Zijlstra
2014-07-16 12:16 ` Paul E. McKenney
2014-07-16 13:05 ` Peter Zijlstra
2014-07-16 13:18 ` Paul E. McKenney
2014-07-16 13:27 ` Mathieu Desnoyers
2014-07-07 22:24 ` [PATCH tip/core/rcu 4/4] documentation: Add pointer to percpu-ref for RCU and refcount Paul E. McKenney
2014-07-08 7:53 ` [PATCH tip/core/rcu 1/4] documentation: Clarify wake-up/memory-barrier relationship Peter Zijlstra
2014-07-08 0:14 ` [PATCH tip/core/rcu 0/4] Documentation changes for 3.17 Josh Triplett
2014-07-08 8:51 ` Lai Jiangshan
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=20140707222345.GA6320@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--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=niv@us.ibm.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sbw@mit.edu \
--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.