netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	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 0/8] xfrm docs update
Date: Sun, 2 Nov 2025 06:54:52 +0700	[thread overview]
Message-ID: <aQadzN8IvCUWWHsF@archie.me> (raw)
In-Reply-To: <c3ee9b5d-62f4-4c7f-b6a4-9e0dd8290edc@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 721 bytes --]

On Sat, Nov 01, 2025 at 11:58:37AM -0700, Randy Dunlap wrote:
> 
> 
> On 11/1/25 2:47 AM, Bagas Sanjaya wrote:
> > Hi,
> > 
> > Here are xfrm documentation patches. Patches [1-6/8] are formatting polishing;
> > [7/8] groups the docs and [8/8] adds MAINTAINERS entries for them.
> > 
> > Enjoy!
> > 
> > Changes since v1 [1]:
> > 
> >   - Also polish xfrm_sync section headings (Randy)
> >   - Apply review trailers (Randy)
> 
> Changes all look good. However, there is still one header that ends
> with ':'. Not sure it is worth fixing.
> 
> XFRM Syscall
>   /proc/sys/net/core/xfrm_* Variables:
> 

I'll also fix it in v3.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2025-11-01 23:54 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
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 [this message]

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=aQadzN8IvCUWWHsF@archie.me \
    --to=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=rdunlap@infradead.org \
    --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;
as well as URLs for NNTP newsgroup(s).