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, darren@dvhart.com, fweisbec@gmail.com,
sbw@mit.edu
Subject: [PATCH tip/core/rcu 0/4] Documentation changes for 3.14
Date: Fri, 15 Nov 2013 16:10:05 -0800 [thread overview]
Message-ID: <20131116001005.GA28191@linux.vnet.ibm.com> (raw)
Hello!
This series contains documentation updates:
1. Fix a typo in Documentation/RCU/trace.txt.
2. Fix formatting blows in kernel-parameters.txt.
3. Fix memory barrier usage in the circular-buffer example.
4. Replace some memory barriers in the circular-buffer example
with load-acquire and store-release to reduce memory-barrier
overhead while still keeping things safe.
Thanx, Paul
b/Documentation/RCU/trace.txt | 2 -
b/Documentation/circular-buffers.txt | 57 +++++++++++++++++++---------------
b/Documentation/kernel-parameters.txt | 9 ++---
3 files changed, 37 insertions(+), 31 deletions(-)
next reply other threads:[~2013-11-16 0:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 0:10 Paul E. McKenney [this message]
2013-11-16 0:10 ` [PATCH tip/core/rcu 1/4] rcu: Fix typo in Documentation/RCU/trace.txt Paul E. McKenney
2013-11-16 0:10 ` [PATCH tip/core/rcu 2/4] rcu: Fix formatting blows in kernel-parameters.txt Paul E. McKenney
2013-11-16 0:10 ` [PATCH tip/core/rcu 3/4] documentation: Fix circular-buffer example Paul E. McKenney
2013-11-16 0:10 ` [PATCH tip/core/rcu 4/4] documentation: Update circular buffer for load-acquire/store-release Paul E. McKenney
2013-11-16 16:03 ` Peter Zijlstra
2013-11-16 20:18 ` Paul E. McKenney
2013-11-16 11:58 ` David Howells
2013-11-16 15:40 ` 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=20131116001005.GA28191@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@kernel.org \
--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
all inboxes | Powered by JetHome®