From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, jiangshanlai@gmail.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/5] Documentation updates for 4.3
Date: Fri, 17 Jul 2015 16:32:24 -0700 [thread overview]
Message-ID: <20150717233224.GA24318@linux.vnet.ibm.com> (raw)
Hello!
This series contains documentation updates for 4.3:
1. Bring rcutorture parameters up to date.
2. Fix spelling of "operators".
3. Fix variable-name typo in memory-barriers.txt.
4. Replace ACCESS_ONCE() by READ_ONCE() and WRITE_ONCE().
5. Call out smp_mb__after_unlock_lock() transitivity. Most likely
just in time to eliminate it entirely, mais c'est la vie!
Thanx, Paul
------------------------------------------------------------------------
b/Documentation/RCU/rcu_dereference.txt | 2
b/Documentation/kernel-parameters.txt | 35 ++-
b/Documentation/memory-barriers.txt | 359 ++++++++++++++++----------------
3 files changed, 209 insertions(+), 187 deletions(-)
next reply other threads:[~2015-07-17 23:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 23:32 Paul E. McKenney [this message]
2015-07-17 23:32 ` [PATCH tip/core/rcu 1/5] documentation: Bring rcutorture parameters up to date Paul E. McKenney
2015-07-17 23:32 ` [PATCH tip/core/rcu 2/5] documentation: Fix spelling of "operators" Paul E. McKenney
2015-07-17 23:32 ` [PATCH tip/core/rcu 3/5] documentation: Fix variable-name typo in memory-barriers.txt Paul E. McKenney
2015-07-17 23:32 ` [PATCH tip/core/rcu 4/5] documentation: Replace ACCESS_ONCE() by READ_ONCE() and WRITE_ONCE() Paul E. McKenney
2015-07-17 23:32 ` [PATCH tip/core/rcu 5/5] doc: Call out smp_mb__after_unlock_lock() transitivity 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=20150717233224.GA24318@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=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--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.