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/4] Documentation updates for 4.8
Date: Wed, 15 Jun 2016 14:38:47 -0700 [thread overview]
Message-ID: <20160615213847.GA3610@linux.vnet.ibm.com> (raw)
Hello!
This series provides a few minor documentation updates for RCU:
1. Add reference to the 2014 RCU API LWN article.
2. Add references to 2010 and 2014 Big API Tables.
3. Add RCU_NONIDLE() restrictions to requirements.
4. Fix a typo, courtesy of Eric Engestrom.
I am still harboring fantasies of getting another block of the RCU design
documentation done in time for the merge window, but it is currently
not yet even ready for review.
Thanx, Paul
------------------------------------------------------------------------
Design/Requirements/Requirements.html | 35 ++++++++++++++++++++++++++++++++++
stallwarn.txt | 2 -
whatisRCU.txt | 3 ++
3 files changed, 39 insertions(+), 1 deletion(-)
next reply other threads:[~2016-06-15 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 21:38 Paul E. McKenney [this message]
2016-06-15 21:39 ` [PATCH tip/core/rcu 1/4] documentation: Add reference to 2014 RCU API LWN article Paul E. McKenney
2016-06-15 21:39 ` [PATCH tip/core/rcu 2/4] documentation: Add references to 2010 and 2014 Big API Tables Paul E. McKenney
2016-06-15 21:39 ` [PATCH tip/core/rcu 3/4] documentation: Add RCU_NONIDLE() restrictions to requirements Paul E. McKenney
2016-06-15 21:39 ` [PATCH tip/core/rcu 4/4] Documentation: Fix spelling mistake 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=20160615213847.GA3610@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox