From: "Paul E. McKenney" <paulmck@kernel.org>
To: rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com,
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/9] Documentation updates for v5.7
Date: Fri, 14 Feb 2020 15:38:48 -0800 [thread overview]
Message-ID: <20200214233848.GA12744@paulmck-ThinkPad-P72> (raw)
Hello!
This series provides documentation updates.
1. Add some more RCU list patterns in the kernel, courtesy of
Joel Fernandes and Amol Grover.
2. Remove remaining HTML tags in ReST files, courtesy of SeongJae
Park.
3. Fix typos in a example code snippets, courtesy of SeongJae Park.
4. Update example function name, courtesy of SeongJae Park.
5. Use ':ref:' for links to other docs, courtesy of SeongJae Park.
6. Use absolute paths for non-rst files, courtesy of SeongJae Park.
7. Use https instead of http if possible, courtesy of SeongJae Park.
8. Add description of rcutorture scripting to torture.txt.
9. Fix memory-barriers.txt typos, courtesy of SeongJae Park.
Thanx, Paul
------------------------------------------------------------------------
RCU/Design/Memory-Ordering/Tree-RCU-Memory-Ordering.rst | 8
RCU/listRCU.rst | 285 ++++++++++++----
RCU/rcu.rst | 18 -
RCU/torture.txt | 147 +++++++-
memory-barriers.txt | 8
5 files changed, 373 insertions(+), 93 deletions(-)
reply other threads:[~2020-02-14 23:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200214233848.GA12744@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--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=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.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).