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@efficios.com,
josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de,
peterz@infradead.org, rostedt@goodmis.org, dhowells@redhat.com,
edumazet@google.com, darren@dvhart.com, fweisbec@gmail.com,
sbw@mit.edu
Subject: [PATCH tip/core/rcu 0/3] Documentation updates for 3.12
Date: Sat, 17 Aug 2013 18:25:22 -0700 [thread overview]
Message-ID: <20130818012522.GA27015@linux.vnet.ibm.com> (raw)
Hello!
This series provides a few documentation updates:
1. Update rcu_barrier() documentation to note that it no longer is
guaranteed to wait for a full grace period. This guarantee was
a victim of energy efficiency.
2. Update RTFP documentation.
3. Fix a control-dependency example in the memory-barriers
documentation.
Thanx, Paul
b/Documentation/RCU/RTFP.txt | 855 +++++++++++++++++++++++-------------
b/Documentation/RCU/rcubarrier.txt | 12
b/Documentation/memory-barriers.txt | 10
3 files changed, 564 insertions(+), 313 deletions(-)
next reply other threads:[~2013-08-18 1:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 1:25 Paul E. McKenney [this message]
2013-08-18 1:25 ` [PATCH tip/core/rcu 1/3] rcu: Fix rcu_barrier() documentation Paul E. McKenney
2013-08-18 1:25 ` [PATCH tip/core/rcu 2/3] rcu: Update RTFP documentation Paul E. McKenney
2013-08-18 2:46 ` Josh Triplett
2013-08-19 0:20 ` Paul E. McKenney
2013-08-19 0:38 ` Josh Triplett
2013-08-19 4:09 ` Paul E. McKenney
2013-08-18 1:25 ` [PATCH tip/core/rcu 3/3] doc: Fix memory-barrier control-dependency example Paul E. McKenney
2013-08-18 2:47 ` [PATCH tip/core/rcu 0/3] Documentation updates for 3.12 Josh Triplett
2013-08-20 7:09 ` Rob Landley
2013-08-20 13:39 ` 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=20130818012522.GA27015@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=darren@dvhart.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.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@elte.hu \
--cc=niv@us.ibm.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 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).