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>,
Randy Dunlap <rdunlap@infradead.org>
Subject: [PATCH net-next v2 6/8] Documentation: xfrm_sync: Number the fifth section
Date: Sat, 1 Nov 2025 16:47:42 +0700 [thread overview]
Message-ID: <20251101094744.46932-7-bagasdotme@gmail.com> (raw)
In-Reply-To: <20251101094744.46932-1-bagasdotme@gmail.com>
Number the fifth section ("Exception to threshold settings") to be
consistent with the rest of sections.
Suggested-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/networking/xfrm_sync.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/networking/xfrm_sync.rst b/Documentation/networking/xfrm_sync.rst
index de4da4707037ea..112f7c102ad043 100644
--- a/Documentation/networking/xfrm_sync.rst
+++ b/Documentation/networking/xfrm_sync.rst
@@ -179,8 +179,8 @@ happened) is set to inform the user what happened.
Note the two flags are mutually exclusive.
The message will always have XFRMA_LTIME_VAL and XFRMA_REPLAY_VAL TLVs.
-Exceptions to threshold settings
---------------------------------
+5) Exceptions to threshold settings
+-----------------------------------
If you have an SA that is getting hit by traffic in bursts such that
there is a period where the timer threshold expires with no packets
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-11-01 9:48 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 ` Bagas Sanjaya [this message]
2025-11-01 18:56 ` [PATCH net-next v2 6/8] Documentation: xfrm_sync: Number the fifth section 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=20251101094744.46932-7-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=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).