All of lore.kernel.org
 help / color / mirror / Atom feed
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.20
Date: Wed, 7 Jan 2015 09:09:50 -0800	[thread overview]
Message-ID: <20150107170950.GA30629@linux.vnet.ibm.com> (raw)

Hello!

This series contains a few documentation updates:

1.	Updates the sysfs path for rcu_cpu_stall_timeout, courtesy of
	Xie XiuQi.

2.	Records limitations of bitfields and small variables, noting
	among other things that safe concurrent update to adjacent
	non-bitfield scalar variables is required by the C11 standard.

3.	Fix typo in memory-barriers.txt, courtesy of Davidlohr Bueso.

							Thanx, Paul

------------------------------------------------------------------------

 b/Documentation/RCU/stallwarn.txt   |    2 -
 b/Documentation/memory-barriers.txt |   46 +++++++++++++++++++++++++++++++++++-
 2 files changed, 46 insertions(+), 2 deletions(-)


             reply	other threads:[~2015-01-07 17:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 17:09 Paul E. McKenney [this message]
2015-01-07 17:10 ` [PATCH tip/core/rcu 1/3] documentation: Update sysfs path for rcu_cpu_stall_timeout Paul E. McKenney
2015-01-07 17:10   ` [PATCH tip/core/rcu 2/3] documentation: Record limitations of bitfields and small variables Paul E. McKenney
2015-01-07 17:10   ` [PATCH tip/core/rcu 3/3] documentation: Fix smp typo in memory-barriers.txt 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=20150107170950.GA30629@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.