All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.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/3] Documentation updates for v5.1
Date: Wed, 9 Jan 2019 13:33:02 -0800	[thread overview]
Message-ID: <20190109213302.GA1723@linux.ibm.com> (raw)

Hello!

This series contains RCU documentation updates:

1.	Record the fact that jiffies_till_sched_qs solicits help from
	cond_resched().

2.	Document that CPU-hotplug notifiers cannot invoke
	synchronize_srcu() or srcu_barrier().

3.	Fix outdated links, courtesy of Junchang Wang.

							Thanx, Paul

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

 RCU/Design/Requirements/Requirements.html |   20 +++++++++++++-------
 RCU/whatisRCU.txt                         |    4 ++--
 admin-guide/kernel-parameters.txt         |   27 ++++++++++++++-------------
 3 files changed, 29 insertions(+), 22 deletions(-)


             reply	other threads:[~2019-01-09 21:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09 21:33 Paul E. McKenney [this message]
2019-01-09 21:37 ` [PATCH tip/core/rcu 1/3] doc: Now jiffies_till_sched_qs solicits help from cond_resched() Paul E. McKenney
2019-01-09 21:37 ` [PATCH tip/core/rcu 2/3] doc: CPU-hotplug notifiers cannot invoke synchronize_srcu() or srcu_barrier() Paul E. McKenney
2019-01-09 21:37 ` [PATCH tip/core/rcu 3/3] doc: Fix outdated links 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=20190109213302.GA1723@linux.ibm.com \
    --to=paulmck@linux.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 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.