From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>, stephen@networkplumber.org
Cc: kuba@kernel.org, Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, David Ahern <dsahern@gmail.com>
Subject: [PATCH iproute2-next 1/2] iplink: fix the gso and gro max_size names in documentation
Date: Thu, 9 Feb 2023 18:44:23 -0500 [thread overview]
Message-ID: <727af35c9bf20f4bf1b363daaf6aecea321eb28f.1675985919.git.lucien.xin@gmail.com> (raw)
In-Reply-To: <cover.1675985919.git.lucien.xin@gmail.com>
The option names for "ip link set" should be gso/gro_max_*
instead of max_gso/gro_*. So fix them in documentation.
Fixes: e4ba36f75201 ("iplink: add ip-link documentation")
Signed-off-by: Xin Long <lucien.xin@gmail.com>
---
man/man8/ip-link.8.in | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/man/man8/ip-link.8.in b/man/man8/ip-link.8.in
index ac33b438..eeddf493 100644
--- a/man/man8/ip-link.8.in
+++ b/man/man8/ip-link.8.in
@@ -88,11 +88,11 @@ ip-link \- network device configuration
.RB "[ " txqueuelen
.IR PACKETS " ]"
.br
-.RB "[ " max_gso_size
+.RB "[ " gso_max_size
.IR BYTES " ]"
-.RB "[ " max_gso_segs
+.RB "[ " gso_max_segs
.IR SEGMENTS " ]"
-.RB "[ " max_gro_size
+.RB "[ " gro_max_size
.IR BYTES " ]"
.br
.RB "[ " name
--
2.31.1
next prev parent reply other threads:[~2023-02-09 23:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 23:44 [PATCH iproute2-next 0/2] iplink: support IPv4 BIG TCP Xin Long
2023-02-09 23:44 ` Xin Long [this message]
2023-02-09 23:44 ` [PATCH iproute2-next 2/2] iplink: add gso and gro max_size attributes for ipv4 Xin Long
2023-02-18 1:50 ` [PATCH iproute2-next 0/2] iplink: support IPv4 BIG TCP patchwork-bot+netdevbpf
2023-02-18 17:12 ` 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=727af35c9bf20f4bf1b363daaf6aecea321eb28f.1675985919.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).