On 11/1/25 2:47 AM, Bagas Sanjaya wrote:
> The first section "Message Structure" has excess underline, while the
> second and third one ("TLVS reflect the different parameters" and
> "Default configurations for the parameters") have trailing colon. Trim
> them.
>
> Suggested-by: Randy Dunlap <rdunlap@infradead.org>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Documentation/networking/xfrm_sync.rst | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/networking/xfrm_sync.rst b/Documentation/networking/xfrm_sync.rst
> index c811c3edfa571a..de4da4707037ea 100644
> --- a/Documentation/networking/xfrm_sync.rst
> +++ b/Documentation/networking/xfrm_sync.rst
> @@ -36,7 +36,7 @@ is not driven by packet arrival.
> - the replay sequence for both inbound and outbound
>
> 1) Message Structure
> -----------------------
> +--------------------
>
> nlmsghdr:aevent_id:optional-TLVs.
>
> @@ -83,8 +83,8 @@ when going from kernel to user space)
> A program needs to subscribe to multicast group XFRMNLGRP_AEVENTS
> to get notified of these events.
>
> -2) TLVS reflect the different parameters:
> ------------------------------------------
> +2) TLVS reflect the different parameters
> +----------------------------------------
>
> a) byte value (XFRMA_LTIME_VAL)
>
> @@ -106,8 +106,8 @@ d) expiry timer (XFRMA_ETIMER_THRESH)
> This is a timer value in milliseconds which is used as the nagle
> value to rate limit the events.
>
> -3) Default configurations for the parameters:
> ----------------------------------------------
> +3) Default configurations for the parameters
> +--------------------------------------------
>
> By default these events should be turned off unless there is
> at least one listener registered to listen to the multicast
--
~Randy