From: sawara04.o@gmail.com
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, corbet@lwn.net,
skhan@linuxfoundation.org
Cc: Kyoji Ogasawara <sawara04.o@gmail.com>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org
Subject: [PATCH net-next 1/2] net/smc: fix indentation in smcr_buf_type section
Date: Thu, 5 Mar 2026 18:22:23 +0900 [thread overview]
Message-ID: <20260305092226.27379-2-sawara04.o@gmail.com> (raw)
In-Reply-To: <20260305092226.27379-1-sawara04.o@gmail.com>
From: Kyoji Ogasawara <sawara04.o@gmail.com>
smcr_buf_type section used inconsistent indentation compared
with the rest of this document.
Signed-off-by: Kyoji Ogasawara <sawara04.o@gmail.com>
---
Documentation/networking/smc-sysctl.rst | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/Documentation/networking/smc-sysctl.rst b/Documentation/networking/smc-sysctl.rst
index 904a910f198e..17b8314c0e5e 100644
--- a/Documentation/networking/smc-sysctl.rst
+++ b/Documentation/networking/smc-sysctl.rst
@@ -23,17 +23,17 @@ autocorking_size - INTEGER
Default: 64K
smcr_buf_type - INTEGER
- Controls which type of sndbufs and RMBs to use in later newly created
- SMC-R link group. Only for SMC-R.
+ Controls which type of sndbufs and RMBs to use in later newly created
+ SMC-R link group. Only for SMC-R.
- Default: 0 (physically contiguous sndbufs and RMBs)
+ Default: 0 (physically contiguous sndbufs and RMBs)
- Possible values:
+ Possible values:
- - 0 - Use physically contiguous buffers
- - 1 - Use virtually contiguous buffers
- - 2 - Mixed use of the two types. Try physically contiguous buffers first.
- If not available, use virtually contiguous buffers then.
+ - 0 - Use physically contiguous buffers
+ - 1 - Use virtually contiguous buffers
+ - 2 - Mixed use of the two types. Try physically contiguous buffers first.
+ If not available, use virtually contiguous buffers then.
smcr_testlink_time - INTEGER
How frequently SMC-R link sends out TEST_LINK LLC messages to confirm
--
2.43.0
next prev parent reply other threads:[~2026-03-05 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 9:22 [PATCH net-next 0/2] smc-sysctl formatting and missing entries sawara04.o
2026-03-05 9:22 ` sawara04.o [this message]
2026-03-05 9:22 ` [PATCH net-next 2/2] net/smc: Add documentation for limit_smc_hs and hs_ctrl sawara04.o
2026-03-05 11:24 ` D. Wythe
2026-03-05 16:40 ` Kyoji Ogasawara
2026-03-06 2:28 ` D. Wythe
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=20260305092226.27379-2-sawara04.o@gmail.com \
--to=sawara04.o@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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhan@linuxfoundation.org \
/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