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 3.18
Date: Thu, 28 Aug 2014 11:12:08 -0700 [thread overview]
Message-ID: <20140828181208.GA22865@linux.vnet.ibm.com> (raw)
Hello!
This series provides a few documentation updates for the newish
control-dependency section for memory-barriers.txt:
1. Fix control-dependency no-transitivity example.
2. Add barrier() to control-dependency example.
3. Fix description of 2-legged-if-based control dependencies.
Thanx, Paul
------------------------------------------------------------------------
b/Documentation/memory-barriers.txt | 140 ++++++++++++++++++------------------
1 file changed, 72 insertions(+), 68 deletions(-)
next reply other threads:[~2014-08-28 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 18:12 Paul E. McKenney [this message]
2014-08-28 18:12 ` [PATCH tip/core/rcu 1/3] memory-barriers: Fix control-ordering no-transitivity example Paul E. McKenney
2014-08-28 18:12 ` [PATCH tip/core/rcu 2/3] memory-barriers: Retain barrier() in fold-to-zero example Paul E. McKenney
2014-08-28 18:12 ` [PATCH tip/core/rcu 3/3] memory-barriers: Fix description of 2-legged-if-based control dependencies Paul E. McKenney
2014-09-07 17:10 ` [PATCH tip/core/rcu 1/3] memory-barriers: Fix control-ordering no-transitivity example Pranith Kumar
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=20140828181208.GA22865@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.