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 0/6] xfrm docs update
Date: Fri, 31 Oct 2025 21:58:33 -0700 [thread overview]
Message-ID: <7148e00e-14c4-4eb7-a940-112e86902bc2@infradead.org> (raw)
In-Reply-To: <20251029082615.39518-1-bagasdotme@gmail.com>
On 10/29/25 1:26 AM, Bagas Sanjaya wrote:
> Hi,
>
> Here are xfrm documentation patches. Patches [1-4/6] are formatting polishing;
> [5/6] groups the docs and [6/6] adds MAINTAINERS entries for them.
>
> Enjoy!
>
> Bagas Sanjaya (6):
> Documentation: xfrm_device: Wrap iproute2 snippets in literal code
> block
> Documentation: xfrm_device: Use numbered list for offloading steps
> Documentation: xfrm_device: Separate hardware offload sublists
> Documentation: xfrm_sync: Properly reindent list text
> net: Move XFRM documentation into its own subdirectory
> MAINTAINERS: Add entry for XFRM documentation
LGTM. Thanks.
for the series:
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
OK, one small nit. 3 of the section headings end with ':'
that should not be there. See xfrm/index.html:
XFRM Framework
XFRM device - offloading the IPsec computations
Overview
Callbacks to implement
Flow
XFRM proc - /proc/net/xfrm_* files
Transformation Statistics
XFRM sync
1) Message Structure
2) TLVS reflect the different parameters:
3) Default configurations for the parameters:
4) Message types
Exceptions to threshold settings
XFRM Syscall
/proc/sys/net/core/xfrm_* Variables:
Oh, and could/should
Exceptions to threshold settings
be numbered, 5) ? It looks odd to be unnumbered.
--
~Randy
next prev parent reply other threads:[~2025-11-01 4:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 8:26 [PATCH net-next 0/6] xfrm docs update Bagas Sanjaya
2025-10-29 8:26 ` [PATCH net-next 1/6] Documentation: xfrm_device: Wrap iproute2 snippets in literal code block Bagas Sanjaya
2025-10-29 8:26 ` [PATCH net-next 2/6] Documentation: xfrm_device: Use numbered list for offloading steps Bagas Sanjaya
2025-10-29 8:26 ` [PATCH net-next 3/6] Documentation: xfrm_device: Separate hardware offload sublists Bagas Sanjaya
2025-10-29 8:26 ` [PATCH net-next 4/6] Documentation: xfrm_sync: Properly reindent list text Bagas Sanjaya
2025-10-29 8:26 ` [PATCH net-next 5/6] net: Move XFRM documentation into its own subdirectory Bagas Sanjaya
2025-10-29 8:26 ` [PATCH net-next 6/6] MAINTAINERS: Add entry for XFRM documentation Bagas Sanjaya
2025-10-30 8:12 ` Steffen Klassert
2025-10-30 15:41 ` Jakub Kicinski
2025-10-30 15:44 ` Jakub Kicinski
2025-10-31 0:12 ` Bagas Sanjaya
2025-10-31 0:51 ` Jakub Kicinski
2025-11-01 4:58 ` Randy Dunlap [this message]
2025-11-01 9:14 ` [PATCH net-next 0/6] xfrm docs update 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=7148e00e-14c4-4eb7-a940-112e86902bc2@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;
as well as URLs for NNTP newsgroup(s).