linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: SeongJae Park <sj38.park@gmail.com>
Cc: corbet@lwn.net, madhuparnabhowmik04@gmail.com,
	rcu@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, SeongJae Park <sjpark@amazon.de>
Subject: Re: [PATCH v3 0/7] Fix trivial nits in RCU docs
Date: Tue, 7 Jan 2020 13:32:50 -0800	[thread overview]
Message-ID: <20200107213250.GE13449@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200106200802.26994-1-sj38.park@gmail.com>

On Mon, Jan 06, 2020 at 09:07:55PM +0100, SeongJae Park wrote:
> From: SeongJae Park <sjpark@amazon.de>
> 
> This patchset fixes trivial nits in the RCU documentations.
> 
> It is based on the latest dev branch of Paul's linux-rcu git repository.
> The Complete git tree is also available at
> https://github.com/sjp38/linux/tree/patches/rcu/docs/2019-12-31/v3.

I have queued these for further review and testing, thank you!

							Thanx, Paul

> Changes from v2
> (https://lore.kernel.org/linux-doc/20200106191852.22973-1-sjpark@amazon.de/)
>  - Apply author email (sjpark@amazon.de) correctly
> 
> Changes from v1
> (https://lore.kernel.org/linux-doc/20191231151549.12797-1-sjpark@amazon.de/)
>  - Add 'Reviewed-by' from Madhuparna
>  - Fix wrong author email address
>  - Rebased on latest dev branch of Paul's linux-rcu git repository.
> 
> 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
> 

      parent reply	other threads:[~2020-01-07 21:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06 20:07 [PATCH v3 0/7] Fix trivial nits in RCU docs SeongJae Park
2020-01-06 20:07 ` [PATCH v3 1/7] doc/RCU/Design: Remove remaining HTML tags in ReST files SeongJae Park
2020-01-06 20:07 ` [PATCH v3 2/7] doc/RCU/listRCU: Fix typos in a example code snippets SeongJae Park
2020-01-06 20:07 ` [PATCH v3 3/7] doc/RCU/listRCU: Update example function name SeongJae Park
2020-01-06 20:07 ` [PATCH v3 4/7] doc/RCU/rcu: Use ':ref:' for links to other docs SeongJae Park
2020-01-06 20:08 ` [PATCH v3 5/7] doc/RCU/rcu: Use absolute paths for non-rst files SeongJae Park
2020-01-06 20:08 ` [PATCH v3 6/7] doc/RCU/rcu: Use https instead of http if possible SeongJae Park
2020-01-06 20:08 ` [PATCH v3 7/7] rcu: Fix typos in beginning comments SeongJae Park
2020-01-07 21:32 ` 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=20200107213250.GE13449@paulmck-ThinkPad-P72 \
    --to=paulmck@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madhuparnabhowmik04@gmail.com \
    --cc=rcu@vger.kernel.org \
    --cc=sj38.park@gmail.com \
    --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).