From: sj38.park@gmail.com
To: paulmck@kernel.org
Cc: corbet@lwn.net, rcu@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, SeongJae Park <sjpark@amazon.de>
Subject: [PATCH 0/7] Fix trivial nits in RCU docs
Date: Tue, 31 Dec 2019 16:15:42 +0100 [thread overview]
Message-ID: <20191231151549.12797-1-sjpark@amazon.de> (raw)
From: SeongJae Park <sjpark@amazon.de>
This patchset fixes trivial nits in the RCU documentations.
SeongJae Park (7):
doc/RCU/Design: Remove remaining HTML tags in ReST files
doc/RCU/listRCU: Fix typos in a example code snippets
doc/RCU/listRCU: Update example function name
doc/RCU/rcu: Use ':ref:' for links to other docs
doc/RCU/rcu: Use absolute paths for non-rst files
doc/RCU/rcu: Use https instead of http if possible
rcu: Fix typos in beginning comments
.../Tree-RCU-Memory-Ordering.rst | 8 ++++----
Documentation/RCU/listRCU.rst | 10 +++++-----
Documentation/RCU/rcu.rst | 18 +++++++++---------
kernel/rcu/srcutree.c | 2 +-
kernel/rcu/tree.c | 4 ++--
5 files changed, 21 insertions(+), 21 deletions(-)
--
2.17.1
next reply other threads:[~2019-12-31 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 15:15 sj38.park [this message]
2019-12-31 15:15 ` [PATCH 1/7] doc/RCU/Design: Remove remaining HTML tags in ReST files sj38.park
2019-12-31 15:15 ` [PATCH 2/7] doc/RCU/listRCU: Fix typos in a example code snippets sj38.park
2019-12-31 15:15 ` [PATCH 3/7] doc/RCU/listRCU: Update example function name sj38.park
2019-12-31 15:15 ` [PATCH 4/7] doc/RCU/rcu: Use ':ref:' for links to other docs sj38.park
2019-12-31 15:15 ` [PATCH 5/7] doc/RCU/rcu: Use absolute paths for non-rst files sj38.park
2019-12-31 15:15 ` [PATCH 6/7] doc/RCU/rcu: Use https instead of http if possible sj38.park
2020-01-06 18:35 ` Paul E. McKenney
2020-01-06 19:02 ` SeongJae Park
2019-12-31 15:15 ` [PATCH 7/7] rcu: Fix typos in beginning comments sj38.park
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=20191231151549.12797-1-sjpark@amazon.de \
--to=sj38.park@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=sjpark@amazon.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).