Re: [PATCH] Documentation: RCU: fix brackets

[Paul E. McKenney]

On Sat, Jun 27, 2026 at 11:26:45AM +0200, Manuel Ebner wrote:
> Remove needless brackets and add missing bracket.
> 
> Signed-off-by: Manuel Ebner <manuelebner@xxxxxxxxxxx>

Good catches, queued, thank you!

							Thanx, Paul

> ---
>  .../Design/Expedited-Grace-Periods/Expedited-Grace-Periods.rst  | 2 +-
>  Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp.svg         | 2 +-
>  Documentation/RCU/Design/Memory-Ordering/TreeRCU-qs.svg         | 2 +-
>  Documentation/RCU/Design/Requirements/Requirements.rst          | 2 +-
>  4 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/RCU/Design/Expedited-Grace-Periods/Expedited-Grace-Periods.rst b/Documentation/RCU/Design/Expedited-Grace-Periods/Expedited-Grace-Periods.rst
> index 414f8a2012d6..cf0f9cdca7e8 100644
> --- a/Documentation/RCU/Design/Expedited-Grace-Periods/Expedited-Grace-Periods.rst
> +++ b/Documentation/RCU/Design/Expedited-Grace-Periods/Expedited-Grace-Periods.rst
> @@ -410,7 +410,7 @@ workqueues (see Documentation/core-api/workqueue.rst).
>  
>  The requesting task still does counter snapshotting and funnel-lock
>  processing, but the task reaching the top of the funnel lock does a
> -``schedule_work()`` (from ``_synchronize_rcu_expedited()`` so that a
> +``schedule_work()`` (from ``_synchronize_rcu_expedited()``) so that a
>  workqueue kthread does the actual grace-period processing. Because
>  workqueue kthreads do not accept POSIX signals, grace-period-wait
>  processing need not allow for POSIX signals. In addition, this approach
> diff --git a/Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp.svg b/Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp.svg
> index d05bc7b27edb..95a66de40ca5 100644
> --- a/Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp.svg
> +++ b/Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp.svg
> @@ -3933,7 +3933,7 @@
>           font-style="normal"
>           y="-3914.085"
>           x="3745.7725"
> -         xml:space="preserve">rcu__report_qs_rdp())</text>
> +         xml:space="preserve">rcu__report_qs_rdp()</text>
>      </g>
>      <g
>         id="g4504-3"
> diff --git a/Documentation/RCU/Design/Memory-Ordering/TreeRCU-qs.svg b/Documentation/RCU/Design/Memory-Ordering/TreeRCU-qs.svg
> index 7d6c5f7e505c..882132680308 100644
> --- a/Documentation/RCU/Design/Memory-Ordering/TreeRCU-qs.svg
> +++ b/Documentation/RCU/Design/Memory-Ordering/TreeRCU-qs.svg
> @@ -815,7 +815,7 @@
>           font-style="normal"
>           y="-3914.085"
>           x="3745.7725"
> -         xml:space="preserve">rcu__report_qs_rdp())</text>
> +         xml:space="preserve">rcu__report_qs_rdp()</text>
>      </g>
>      <g
>         id="g4504-3"
> diff --git a/Documentation/RCU/Design/Requirements/Requirements.rst b/Documentation/RCU/Design/Requirements/Requirements.rst
> index 8a216e4a46a7..8101fe6229d5 100644
> --- a/Documentation/RCU/Design/Requirements/Requirements.rst
> +++ b/Documentation/RCU/Design/Requirements/Requirements.rst
> @@ -2785,7 +2785,7 @@ both srcu_read_lock() and srcu_read_unlock().  This need is handled by
>  a Tasks Trace RCU API implemented as thin wrappers around SRCU-fast,
>  which avoids the read-side memory barriers, at least for architectures
>  that apply noinstr to kernel entry/exit code (or that build with
> -``CONFIG_TASKS_TRACE_RCU_NO_MB=y``.
> +``CONFIG_TASKS_TRACE_RCU_NO_MB=y``).
>  
>  Now that the implementation is based on SRCU-fast, a call
>  to synchronize_rcu_tasks_trace() implies at least one call to
> -- 
> 2.54.0
>