From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>, rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com, rostedt@goodmis.org
Subject: Re: [PATCH 1/3] doc: Update whatisRCU.rst for recent RCU API additions
Date: Sat, 16 Aug 2025 10:54:04 +0700 [thread overview]
Message-ID: <aKAA3OHvISThlUX-@archie.me> (raw)
In-Reply-To: <20250816000007.2622326-1-paulmck@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
On Fri, Aug 15, 2025 at 05:00:05PM -0700, Paul E. McKenney wrote:
> +RCU: Initialization/cleanup/ordering::
> +
> + RCU_INIT_POINTER
> + RCU_INITIALIZER
> + RCU_POINTER_INITIALIZER
> + init_rcu_head
> + destroy_rcu_head
> + init_rcu_head_on_stack
> + destroy_rcu_head_on_stack
> + SLAB_TYPESAFE_BY_RCU
> +
> +
> +RCU: Quiescents states and control::
> +
> + cond_resched_tasks_rcu_qs
> + rcu_all_qs
> + rcu_softirq_qs_periodic
> + rcu_end_inkernel_boot
> + rcu_expedite_gp
> + rcu_gp_is_expedited
> + rcu_unexpedite_gp
> + rcu_cpu_stall_reset
> + rcu_head_after_call_rcu
> + rcu_is_watching
> +
> +
> +RCU-sync primitive:
> +
> + rcu_sync_is_idle
> + rcu_sync_init
> + rcu_sync_enter
> + rcu_sync_exit
> + rcu_sync_dtor
Looks like inconsistent (normal paragraph instead of literal code block like
the rest).
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-08-16 3:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 23:59 [PATCH 0/3] rcu: Documentation updates for v6.18 Paul E. McKenney
2025-08-16 0:00 ` [PATCH 1/3] doc: Update whatisRCU.rst for recent RCU API additions Paul E. McKenney
2025-08-16 3:54 ` Bagas Sanjaya [this message]
2025-08-16 4:54 ` Paul E. McKenney
2025-08-16 5:38 ` Bagas Sanjaya
2025-08-16 11:28 ` Paul E. McKenney
2025-08-16 0:00 ` [PATCH 2/3] doc: Add RCU guards to checklist.rst Paul E. McKenney
2025-08-16 0:00 ` [PATCH 3/3] rcu: docs: Requirements.rst: Abide by conventions of kernel documentation Paul E. McKenney
2025-08-16 1:30 ` Akira Yokosawa
2025-08-16 2:02 ` Paul E. McKenney
2025-09-18 10:14 ` [PATCH 0/3] rcu: Documentation updates for v6.18 Paul E. McKenney
2025-09-18 10:14 ` [PATCH v2 1/8] doc: Update whatisRCU.rst for recent RCU API additions Paul E. McKenney
2025-09-18 10:14 ` [PATCH v2 2/8] doc: Add RCU guards to checklist.rst Paul E. McKenney
2025-09-18 10:14 ` [PATCH v2 3/8] rcu: docs: Requirements.rst: Abide by conventions of kernel documentation Paul E. McKenney
2025-09-18 10:14 ` [PATCH v2 4/8] Documentation: RCU: Wrap kvm-remote.sh rerun snippet in literal code block Paul E. McKenney
2025-09-18 10:14 ` [PATCH v2 5/8] Documentation: RCU: Reduce toctree depth Paul E. McKenney
2025-09-18 10:14 ` [PATCH v2 6/8] Documentation: RCU: Retitle toctree index Paul E. McKenney
2025-09-18 10:14 ` [PATCH v2 7/8] doc: Fix typo in RCU's torture.rst documentation Paul E. McKenney
2025-09-18 10:14 ` [PATCH v2 8/8] docs: rcu: Replace multiple dead OLS links in RTFP.txt 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=aKAA3OHvISThlUX-@archie.me \
--to=bagasdotme@gmail.com \
--cc=kernel-team@meta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox