From: Bagas Sanjaya <bagasdotme@gmail.com>
To: paulmck@kernel.org, rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com, rostedt@goodmis.org
Subject: Re: [PATCH rcu 0/2] Documentation updates for v5.19
Date: Tue, 19 Apr 2022 14:08:48 +0700 [thread overview]
Message-ID: <371488b0-1baf-8cea-628f-83c9b0383c88@gmail.com> (raw)
In-Reply-To: <20220418225004.GA3944767@paulmck-ThinkPad-P17-Gen-1>
On 4/19/22 05:50, Paul E. McKenney wrote:
> Hello!
>
> This series contains a couple of documentation updates:
>
> 1. Add documentation for rude and trace RCU flavors.
>
> 2. Update RCU cross-references as suggested in doc-guide, courtesy
> of Akira Yokosawa.
>
Bulding htmldocs with this series, no new warnings found.
Tested-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-04-19 7:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 22:50 [PATCH rcu 0/2] Documentation updates for v5.19 Paul E. McKenney
2022-04-18 22:50 ` [PATCH rcu 1/2] docs: Add documentation for rude and trace RCU flavors Paul E. McKenney
2022-04-20 15:32 ` Steven Rostedt
2022-04-20 16:13 ` Paul E. McKenney
2022-04-20 16:16 ` Steven Rostedt
2022-04-20 16:19 ` Steven Rostedt
2022-04-20 16:48 ` Paul E. McKenney
2022-04-20 18:02 ` Steven Rostedt
2022-04-20 18:37 ` Paul E. McKenney
2022-04-20 18:43 ` Steven Rostedt
2022-04-20 19:22 ` Paul E. McKenney
2022-04-18 22:50 ` [PATCH rcu 2/2] docs: Update RCU cross-references as suggested in doc-guide Paul E. McKenney
2022-04-19 7:08 ` Bagas Sanjaya [this message]
2022-04-19 14:23 ` [PATCH rcu 0/2] Documentation updates for v5.19 Paul E. McKenney
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=371488b0-1baf-8cea-628f-83c9b0383c88@gmail.com \
--to=bagasdotme@gmail.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.