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 0/6] xfrm docs update
Date: Wed, 29 Oct 2025 15:26:08 +0700 [thread overview]
Message-ID: <20251029082615.39518-1-bagasdotme@gmail.com> (raw)
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
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 | 83 ++++++++++---------
.../networking/{ => xfrm}/xfrm_sysctl.rst | 0
MAINTAINERS | 1 +
7 files changed, 70 insertions(+), 52 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 (68%)
rename Documentation/networking/{ => xfrm}/xfrm_sysctl.rst (100%)
base-commit: 61958b33ef0bab1c1874c933cd3910f495526782
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2025-10-29 8:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 8:26 Bagas Sanjaya [this message]
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 ` [PATCH net-next 0/6] xfrm docs update Randy Dunlap
2025-11-01 9:14 ` 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=20251029082615.39518-1-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).