mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux Networking <netdev@vger.kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH net-next v2 5/8] Documentation: xfrm_sync: Trim excess section heading characters
Date: Sat, 1 Nov 2025 11:56:23 -0700	[thread overview]
Message-ID: <d5db214c-8216-4f6a-a64c-8a636f194202@infradead.org> (raw)
In-Reply-To: <20251101094744.46932-6-bagasdotme@gmail.com>



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

  reply	other threads:[~2025-11-01 18:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-01  9:47 [PATCH net-next v2 0/8] xfrm docs update Bagas Sanjaya
2025-11-01  9:47 ` [PATCH net-next v2 1/8] Documentation: xfrm_device: Wrap iproute2 snippets in literal code block Bagas Sanjaya
2025-11-01  9:47 ` [PATCH net-next v2 2/8] Documentation: xfrm_device: Use numbered list for offloading steps Bagas Sanjaya
2025-11-01  9:47 ` [PATCH net-next v2 3/8] Documentation: xfrm_device: Separate hardware offload sublists Bagas Sanjaya
2025-11-01  9:47 ` [PATCH net-next v2 4/8] Documentation: xfrm_sync: Properly reindent list text Bagas Sanjaya
2025-11-01  9:47 ` [PATCH net-next v2 5/8] Documentation: xfrm_sync: Trim excess section heading characters Bagas Sanjaya
2025-11-01 18:56   ` Randy Dunlap [this message]
2025-11-01  9:47 ` [PATCH net-next v2 6/8] Documentation: xfrm_sync: Number the fifth section Bagas Sanjaya
2025-11-01 18:56   ` Randy Dunlap
2025-11-01  9:47 ` [PATCH net-next v2 7/8] net: Move XFRM documentation into its own subdirectory Bagas Sanjaya
2025-11-01  9:47 ` [PATCH net-next v2 8/8] MAINTAINERS: Add entry for XFRM documentation Bagas Sanjaya
2025-11-01 18:58 ` [PATCH net-next v2 0/8] xfrm docs update Randy Dunlap
2025-11-01 23:54   ` Bagas Sanjaya

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=d5db214c-8216-4f6a-a64c-8a636f194202@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=steffen.klassert@secunet.com \
    /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

all inboxes | Powered by JetHome®