From: Nicolas Escande <nico.escande@gmail.com>
To: stephen@networkplumber.org
Cc: netdev@vger.kernel.org, Nicolas Escande <nico.escande@gmail.com>
Subject: [iproute2] man: bridge: update bridge link show
Date: Thu, 27 Jul 2023 19:22:08 +0200 [thread overview]
Message-ID: <20230727172208.2494176-1-nico.escande@gmail.com> (raw)
This adds the missing [ master DEVICE ] in the synopsis part and the detailed
usage/effects of [ dev DEV ] & [ master DEVICE ] int the detailed syntax part
Signed-off-by: Nicolas Escande <nico.escande@gmail.com>
---
man/man8/bridge.8 | 15 ++++++++++++---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/man/man8/bridge.8 b/man/man8/bridge.8
index e0552819..4e7371fc 100644
--- a/man/man8/bridge.8
+++ b/man/man8/bridge.8
@@ -66,7 +66,10 @@ bridge \- show / manipulate bridge addresses and devices
.ti -8
.BR "bridge link" " [ " show " ] [ "
.B dev
-.IR DEV " ]"
+.IR DEV " ] ["
+.B master
+.IR DEVICE " ]"
+
.ti -8
.BR "bridge fdb" " { " add " | " append " | " del " | " replace " } "
@@ -661,9 +664,15 @@ display current time when using monitor option.
.SS bridge link show - list ports configuration for all bridges.
-This command displays port configuration and flags for all bridges.
+This command displays ports configuration and flags for all bridges by default.
-To display port configuration and flags for a specific bridge, use the
+.TP
+.BI dev " DEV"
+only display the specific bridge port named DEV.
+
+.TP
+.BI master " DEVICE"
+only display ports of the bridge named DEVICE. This is quite similar to
"ip link show master <bridge_device>" command.
.SH bridge fdb - forwarding database management
--
2.41.0
next reply other threads:[~2023-07-27 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 17:22 Nicolas Escande [this message]
2023-07-30 10:29 ` [iproute2] man: bridge: update bridge link show Ido Schimmel
2023-08-04 16:46 ` Nicolas Escande
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=20230727172208.2494176-1-nico.escande@gmail.com \
--to=nico.escande@gmail.com \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox