From: Ido Schimmel <idosch@nvidia.com>
To: netdev@vger.kernel.org
Cc: stephen@networkplumber.org, dsahern@gmail.com,
netdev@kapio-technology.com, Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH iproute2] ip: bridge_slave: Fix help message indentation
Date: Wed, 19 Apr 2023 18:43:59 +0300 [thread overview]
Message-ID: <20230419154359.2656173-1-idosch@nvidia.com> (raw)
Use tabs instead of spaces to be consistent with the rest of the
options.
Before:
$ ip link help bridge_slave
Usage: ... bridge_slave [ fdb_flush ]
[...]
[ vlan_tunnel {on | off} ]
[ isolated {on | off} ]
[ locked {on | off} ]
[ mab {on | off} ]
[ backup_port DEVICE ] [ nobackup_port ]
After:
$ ip link help bridge_slave
Usage: ... bridge_slave [ fdb_flush ]
[...]
[ vlan_tunnel {on | off} ]
[ isolated {on | off} ]
[ locked {on | off} ]
[ mab {on | off} ]
[ backup_port DEVICE ] [ nobackup_port ]
Fixes: 05f1164fe811 ("bridge: link: Add MAC Authentication Bypass (MAB) support")
Signed-off-by: Ido Schimmel <idosch@nvidia.com>
---
ip/iplink_bridge_slave.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ip/iplink_bridge_slave.c b/ip/iplink_bridge_slave.c
index 43b429485502..66a67961957f 100644
--- a/ip/iplink_bridge_slave.c
+++ b/ip/iplink_bridge_slave.c
@@ -40,7 +40,7 @@ static void print_explain(FILE *f)
" [ vlan_tunnel {on | off} ]\n"
" [ isolated {on | off} ]\n"
" [ locked {on | off} ]\n"
- " [ mab {on | off} ]\n"
+ " [ mab {on | off} ]\n"
" [ backup_port DEVICE ] [ nobackup_port ]\n"
);
}
--
2.37.3
next reply other threads:[~2023-04-19 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 15:43 Ido Schimmel [this message]
2023-04-21 14:06 ` [PATCH iproute2] ip: bridge_slave: Fix help message indentation Simon Horman
2023-04-22 3:20 ` 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=20230419154359.2656173-1-idosch@nvidia.com \
--to=idosch@nvidia.com \
--cc=dsahern@gmail.com \
--cc=netdev@kapio-technology.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 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.