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>,
Abdelrahman Fekry <abdelrahmanfekry375@gmail.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH net-next 3/5] net: ip-sysctl: Format pf_{enable,expose} boolean lists as bullet lists
Date: Tue, 1 Jul 2025 10:12:58 +0700 [thread overview]
Message-ID: <20250701031300.19088-4-bagasdotme@gmail.com> (raw)
In-Reply-To: <20250701031300.19088-1-bagasdotme@gmail.com>
These lists' items were separated by newlines but without bullet list
marker. Turn the lists into proper bullet list.
While at it, also reword values description for pf_expose to not repeat
mentioning SCTP_PEER_ADDR_CHANGE and SCTP_GET_PEER_ADDR_INFO sockopt.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/networking/ip-sysctl.rst | 28 +++++++++++---------------
1 file changed, 12 insertions(+), 16 deletions(-)
diff --git a/Documentation/networking/ip-sysctl.rst b/Documentation/networking/ip-sysctl.rst
index 6c2bb3347885c3..774fbf462ccd65 100644
--- a/Documentation/networking/ip-sysctl.rst
+++ b/Documentation/networking/ip-sysctl.rst
@@ -3326,31 +3326,27 @@ pf_enable - INTEGER
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-failover for
details.
- 1: Enable pf.
+ Possible values:
- 0: Disable pf.
+ - 1: Enable pf.
+ - 0: Disable pf.
Default: 1
pf_expose - INTEGER
Unset or enable/disable pf (pf is short for potentially failed) state
exposure. Applications can control the exposure of the PF path state
- in the SCTP_PEER_ADDR_CHANGE event and the SCTP_GET_PEER_ADDR_INFO
- sockopt. When it's unset, no SCTP_PEER_ADDR_CHANGE event with
- SCTP_ADDR_PF state will be sent and a SCTP_PF-state transport info
- can be got via SCTP_GET_PEER_ADDR_INFO sockopt; When it's enabled,
- a SCTP_PEER_ADDR_CHANGE event will be sent for a transport becoming
- SCTP_PF state and a SCTP_PF-state transport info can be got via
- SCTP_GET_PEER_ADDR_INFO sockopt; When it's disabled, no
- SCTP_PEER_ADDR_CHANGE event will be sent and it returns -EACCES when
- trying to get a SCTP_PF-state transport info via SCTP_GET_PEER_ADDR_INFO
- sockopt.
+ in the SCTP_PEER_ADDR_CHANGE event and access of SCTP_PF-state
+ transport info via SCTP_GET_PEER_ADDR_INFO sockopt.
- 0: Unset pf state exposure, Compatible with old applications.
+ Possible values:
- 1: Disable pf state exposure.
-
- 2: Enable pf state exposure.
+ - 0: Unset pf state exposure (compatible with old applications). No
+ event will be sent but the transport info can be queried.
+ - 1: Disable pf state exposure. No event will be sent and trying to
+ obtain transport info will return -EACCESS.
+ - 2: Enable pf state exposure. The event will be sent for a transport
+ becoming SCTP_PF state and transport info can be obtained.
Default: 0
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-07-01 3:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 3:12 [PATCH net-next 0/5] Another ip-sysctl docs cleanup Bagas Sanjaya
2025-07-01 3:12 ` [PATCH net-next 1/5] net: ip-sysctl: Format Private VLAN proxy arp aliases as bullet list Bagas Sanjaya
2025-07-01 14:16 ` Simon Horman
2025-07-01 3:12 ` [PATCH net-next 2/5] net: ip-sysctl: Format possible value range of ioam6_id{,_wide} " Bagas Sanjaya
2025-07-01 14:16 ` Simon Horman
2025-07-01 3:12 ` Bagas Sanjaya [this message]
2025-07-01 14:16 ` [PATCH net-next 3/5] net: ip-sysctl: Format pf_{enable,expose} boolean lists as bullet lists Simon Horman
2025-07-01 3:12 ` [PATCH net-next 4/5] net: ip-sysctl: Format SCTP-related memory parameters description as bullet list Bagas Sanjaya
2025-07-01 14:17 ` Simon Horman
2025-07-01 3:13 ` [PATCH net-next 5/5] net: ip-sysctl: Add link to SCTP IPv4 scoping draft Bagas Sanjaya
2025-07-01 14:17 ` Simon Horman
2025-07-03 14:00 ` [PATCH net-next 0/5] Another ip-sysctl docs cleanup patchwork-bot+netdevbpf
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=20250701031300.19088-4-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=abdelrahmanfekry375@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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 \
/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
all inboxes | Powered by JetHome®