From: Josh Triplett <josh@joshtriplett.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.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,
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 0/5] Documentation changes for 4.4
Date: Tue, 6 Oct 2015 10:35:05 -0700 [thread overview]
Message-ID: <20151006173505.GI9600@cloud> (raw)
In-Reply-To: <20151006163358.GA14407@linux.vnet.ibm.com>
On Tue, Oct 06, 2015 at 09:33:58AM -0700, Paul E. McKenney wrote:
> Hello!
>
> This series contains a few documentation updates:
>
> 1. Clearly state that RCU readers have no acquire/release semantics.
>
> 2. Call out slow consoles as a cause of stall warnings.
>
> 3. Update whatisRCU() to show rcu_dereference_protected(),
> courtesy of Jason A. Donenfeld.
>
> 4. Catch up list of torture_type options.
>
> 5. Add lockless_dereference() to memory-barriers.txt.
For all five:
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
prev parent reply other threads:[~2015-10-06 17:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 16:33 [PATCH tip/core/rcu 0/5] Documentation changes for 4.4 Paul E. McKenney
2015-10-06 16:34 ` [PATCH tip/core/rcu 1/5] documentation: No acquire/release for RCU readers Paul E. McKenney
2015-10-06 16:34 ` [PATCH tip/core/rcu 2/5] documentation: Call out slow consoles as cause of stall warnings Paul E. McKenney
2015-10-06 16:34 ` [PATCH tip/core/rcu 3/5] documentation: Correct doc to use rcu_dereference_protected Paul E. McKenney
2015-10-06 16:34 ` [PATCH tip/core/rcu 4/5] documentation: Catch up list of torture_type options Paul E. McKenney
2015-10-06 16:34 ` [PATCH tip/core/rcu 5/5] documentation: Add lockless_dereference() Paul E. McKenney
2015-10-06 17:35 ` Josh Triplett [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=20151006173505.GI9600@cloud \
--to=josh@joshtriplett.org \
--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=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).