public inbox for linux-kernel@vger.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, 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,
	fweisbec@gmail.com, oleg@redhat.com, joel@joelfernandes.org
Subject: [PATCH tip/core/rcu 0/6] Documentation updates for v4.20/v5.0
Date: Wed, 29 Aug 2018 14:16:37 -0700	[thread overview]
Message-ID: <20180829211637.GA20980@linux.vnet.ibm.com> (raw)

Hello!

This series contains documentation updates.  Some of these describe changes
that are carried out in another branch, but are kept separate to allow
reviewers to easily find the intent of those changes.

1.	Add design documentation on interruption of NMI handlers.

2.	Fix broken RCU-requirements link to LKML archive, courtesy of
	Joel Fernandes.

3.	Improve rcu_dynticks::dynticks documentation, courtesy of
	Joel Fernandes.

4.	Update documentation for removal of RCU-bh update machinery.

5.	Fix broken HTML directive.

6.	Update documentation for removal of RCU-sched update machinery.

							Thanx, Paul

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

 RCU/Design/Data-Structures/Data-Structures.html                 |    8 
 RCU/Design/Expedited-Grace-Periods/Expedited-Grace-Periods.html |    9 
 RCU/Design/Requirements/Requirements.html                       |  164 ++--------
 RCU/stallwarn.txt                                               |   13 
 RCU/whatisRCU.txt                                               |    3 
 admin-guide/kernel-parameters.txt                               |   16 
 kernel-per-CPU-kthreads.txt                                     |    2 
 7 files changed, 73 insertions(+), 142 deletions(-)


             reply	other threads:[~2018-08-29 21:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 21:16 Paul E. McKenney [this message]
2018-08-29 21:17 ` [PATCH tip/core/rcu 1/6] doc: Add design documentation on interruption of NMI handlers Paul E. McKenney
2018-08-29 21:17 ` [PATCH tip/core/rcu 2/6] doc: Fix broken RCU-requirements link to LKML archive Paul E. McKenney
2018-08-29 21:17 ` [PATCH tip/core/rcu 3/6] doc: Improve rcu_dynticks::dynticks documentation Paul E. McKenney
2018-08-29 21:17 ` [PATCH tip/core/rcu 4/6] doc: Update documentation for removal of RCU-bh update machinery Paul E. McKenney
2018-08-30 18:22   ` Paul E. McKenney
2018-08-29 21:17 ` [PATCH tip/core/rcu 5/6] doc: Fix broken HTML directive Paul E. McKenney
2018-08-29 21:17 ` [PATCH tip/core/rcu 6/6] doc: Update documentation for removal of RCU-sched update machinery 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=20180829211637.GA20980@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=edumazet@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --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