From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: linux-kernel@vger.kernel.org, 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: Re: [PATCH tip/core/rcu 10/10] documentation: Add documentation for RCU's major data structures
Date: Sat, 16 Apr 2016 19:33:56 -0700 [thread overview]
Message-ID: <20160417023356.GH3687@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160416145239.GA13055@fixme-laptop.cn.ibm.com>
On Sat, Apr 16, 2016 at 10:52:39PM +0800, Boqun Feng wrote:
> Hi Paul,
>
> On Tue, Apr 12, 2016 at 08:18:21AM -0700, Paul E. McKenney wrote:
> > This commit adds documentation for RCU's major data structures,
> > including rcu_state, rcu_node, rcu_data, rcu_dynticks, and rcu_head.
> >
>
> One small thing, you are using term TREE_PREEMPT_RCU throughout the
> whole document, while I think it has been removed in commit
> 28f6569ab7d03 ("rcu: Remove redundant TREE_PREEMPT_RCU config option").
>
> so, a "s/TREE_PREEMPT_RCU/PREEMPT_RCU" makes the document more up to
> date?
Good catch, will fix!
Thanx, Paul
> Regards,
> Boqun
>
> > Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > ---
> [...]
prev parent reply other threads:[~2016-04-17 2:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 15:17 [PATCH tip/core/rcu 0/10] Documentation updates for 4.7 Paul E. McKenney
2016-04-12 15:18 ` [PATCH tip/core/rcu 01/10] documentation: Make sample code and documentation consistent Paul E. McKenney
2016-04-12 15:18 ` [PATCH tip/core/rcu 02/10] documentation: Add real-time requirements from CPU-bound workloads Paul E. McKenney
2016-04-12 15:18 ` [PATCH tip/core/rcu 03/10] documentation: Add synchronize_rcu_mult() to the requirements Paul E. McKenney
2016-04-12 15:18 ` [PATCH tip/core/rcu 04/10] documentation: Explain why rcu_read_lock() needs no barrier() Paul E. McKenney
2016-04-12 15:18 ` [PATCH tip/core/rcu 05/10] documentation: Document illegality of call_rcu() from offline CPUs Paul E. McKenney
2016-04-12 15:18 ` [PATCH tip/core/rcu 06/10] documentation: Remove unnecessary images from requirements Paul E. McKenney
2016-04-12 15:18 ` [PATCH tip/core/rcu 07/10] documentation: Get rid of duplicate .htmlx file Paul E. McKenney
2016-04-12 15:18 ` [PATCH tip/core/rcu 08/10] documentation: Sharpen up the no-readers quick quiz Paul E. McKenney
2016-04-12 15:18 ` [PATCH tip/core/rcu 09/10] documentation: Emphasize the call_rcu() is illegal from idle Paul E. McKenney
2016-04-12 15:18 ` [PATCH tip/core/rcu 10/10] documentation: Add documentation for RCU's major data structures Paul E. McKenney
2016-04-16 14:52 ` Boqun Feng
2016-04-17 2:33 ` Paul E. McKenney [this message]
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=20160417023356.GH3687@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=boqun.feng@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