From: Bagas Sanjaya <bagasdotme@gmail.com>
To: 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>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH net-next v3 0/9] xfrm docs update
Date: Mon, 3 Nov 2025 08:50:21 +0700 [thread overview]
Message-ID: <20251103015029.17018-2-bagasdotme@gmail.com> (raw)
Hi,
Here are xfrm documentation patches. Patches [1-7/9] are formatting polishing;
[8/9] groups the docs and [9/9] adds MAINTAINERS entries for them.
Enjoy!
Changes since v2 [1]:
- Also trim trailing colon in xfrm_sysctl section heading (Randy)
[1]: https://lore.kernel.org/linux-doc/20251101094744.46932-1-bagasdotme@gmail.com/
Bagas Sanjaya (9):
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
Documentation: xfrm_sync: Trim excess section heading characters
Documentation: xfrm_sysctl: Trim trailing colon in section heading
Documentation: xfrm_sync: Number the fifth section
net: Move XFRM documentation into its own subdirectory
MAINTAINERS: Add entry for XFRM documentation
Documentation/networking/index.rst | 5 +-
Documentation/networking/xfrm/index.rst | 13 +++
.../networking/{ => xfrm}/xfrm_device.rst | 20 ++--
.../networking/{ => xfrm}/xfrm_proc.rst | 0
.../networking/{ => xfrm}/xfrm_sync.rst | 97 ++++++++++---------
.../networking/{ => xfrm}/xfrm_sysctl.rst | 4 +-
MAINTAINERS | 1 +
7 files changed, 79 insertions(+), 61 deletions(-)
create mode 100644 Documentation/networking/xfrm/index.rst
rename Documentation/networking/{ => xfrm}/xfrm_device.rst (95%)
rename Documentation/networking/{ => xfrm}/xfrm_proc.rst (100%)
rename Documentation/networking/{ => xfrm}/xfrm_sync.rst (64%)
rename Documentation/networking/{ => xfrm}/xfrm_sysctl.rst (68%)
base-commit: 01cc760632b875c4ad0d8fec0b0c01896b8a36d4
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2025-11-03 1:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 1:50 Bagas Sanjaya [this message]
2025-11-03 1:50 ` [PATCH net-next v3 1/9] Documentation: xfrm_device: Wrap iproute2 snippets in literal code block Bagas Sanjaya
2025-11-03 1:50 ` [PATCH net-next v3 2/9] Documentation: xfrm_device: Use numbered list for offloading steps Bagas Sanjaya
2025-11-03 1:50 ` [PATCH net-next v3 3/9] Documentation: xfrm_device: Separate hardware offload sublists Bagas Sanjaya
2025-11-03 1:50 ` [PATCH net-next v3 4/9] Documentation: xfrm_sync: Properly reindent list text Bagas Sanjaya
2025-11-03 1:50 ` [PATCH net-next v3 5/9] Documentation: xfrm_sync: Trim excess section heading characters Bagas Sanjaya
2025-11-03 1:50 ` [PATCH net-next v3 6/9] Documentation: xfrm_sysctl: Trim trailing colon in section heading Bagas Sanjaya
2025-11-04 0:11 ` Randy Dunlap
2025-11-03 1:50 ` [PATCH net-next v3 7/9] Documentation: xfrm_sync: Number the fifth section Bagas Sanjaya
2025-11-03 1:50 ` [PATCH net-next v3 8/9] net: Move XFRM documentation into its own subdirectory Bagas Sanjaya
2025-11-03 1:50 ` [PATCH net-next v3 9/9] MAINTAINERS: Add entry for XFRM documentation Bagas Sanjaya
2025-11-10 23:39 ` [PATCH net-next v3 0/9] xfrm docs update Bagas Sanjaya
2025-11-11 0:08 ` Jakub Kicinski
2025-11-11 2:31 ` Bagas Sanjaya
2025-11-13 10:34 ` Steffen Klassert
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=20251103015029.17018-2-bagasdotme@gmail.com \
--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=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).