From: Joachim Wiberg <troglobit@gmail.com>
To: netdev@vger.kernel.org
Cc: David Ahern <dsahern@kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>,
Nikolay Aleksandrov <razor@blackwall.org>,
Joachim Wiberg <troglobit@gmail.com>
Subject: [PATCH iproute2-next v3 7/7] man: ip-link: whitespace fixes to odd line breaks mid sentence
Date: Wed, 9 Mar 2022 20:23:16 +0100 [thread overview]
Message-ID: <20220309192316.2918792-8-troglobit@gmail.com> (raw)
In-Reply-To: <20220309192316.2918792-1-troglobit@gmail.com>
Some options, spread across the man page, were accidentally (?) space
indented (possible bullet list auto-indent in editors), causing odd line
breaks in presentation mode (emacs, nroff, etc.). This patch aligns the
multi-line descriptions to column zero, in line with other such option
descriptions.
Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
---
man/man8/ip-link.8.in | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/man/man8/ip-link.8.in b/man/man8/ip-link.8.in
index 1237ff4c..c142d80a 100644
--- a/man/man8/ip-link.8.in
+++ b/man/man8/ip-link.8.in
@@ -481,11 +481,11 @@ where <phy_dev> is the physical device to which VLAN device is bound.
.BR gvrp " { " on " | " off " } "
- specifies whether this VLAN should be registered using GARP VLAN
- Registration Protocol.
+Registration Protocol.
.BR mvrp " { " on " | " off " } "
- specifies whether this VLAN should be registered using Multiple VLAN
- Registration Protocol.
+Registration Protocol.
.BR loose_binding " { " on " | " off " } "
- specifies whether the VLAN device state is bound to the physical device state.
@@ -2189,9 +2189,9 @@ parameter must be specified.
.sp
.BI query_rss " on|off"
- toggle the ability of querying the RSS configuration of a specific
- VF. VF RSS information like RSS hash key may be considered sensitive
- on some devices where this information is shared between VF and PF
- and thus its querying may be prohibited by default.
+VF. VF RSS information like RSS hash key may be considered sensitive
+on some devices where this information is shared between VF and PF
+and thus its querying may be prohibited by default.
.sp
.BI state " auto|enable|disable"
- set the virtual link state as seen by the specified VF. Setting to
@@ -2458,11 +2458,11 @@ this flag is on.
.BR mcast_flood " { " on " | " off " }"
- controls whether a given port will flood multicast traffic for which
- there is no MDB entry. By default this flag is on.
+there is no MDB entry. By default this flag is on.
.BR mcast_to_unicast " { " on " | " off " }"
- controls whether a given port will replicate packets using unicast
- instead of multicast. By default this flag is off.
+instead of multicast. By default this flag is off.
.BI group_fwd_mask " MASK "
- set the group forward mask. This is the bitmask that is applied to
--
2.25.1
next prev parent reply other threads:[~2022-03-09 19:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 19:23 [PATCH iproute2-next v3 0/7] bridge: support for controlling broadcast flooding per port Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 1/7] bridge: support for controlling flooding of broadcast " Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 2/7] man: bridge: document new bcast_flood flag for bridge ports Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 3/7] man: bridge: add missing closing " in bridge show mdb Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 4/7] ip: iplink_bridge_slave: support for broadcast flooding Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 5/7] man: ip-link: document new bcast_flood flag on bridge ports Joachim Wiberg
2022-03-09 19:23 ` [PATCH iproute2-next v3 6/7] man: ip-link: mention bridge port's default mcast_flood state Joachim Wiberg
2022-03-09 19:23 ` Joachim Wiberg [this message]
2022-03-10 9:01 ` [PATCH iproute2-next v3 0/7] bridge: support for controlling broadcast flooding per port Nikolay Aleksandrov
2022-03-12 16:10 ` 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=20220309192316.2918792-8-troglobit@gmail.com \
--to=troglobit@gmail.com \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.