From: Phil Sutter <phil@nwl.cc>
To: Stephen Hemminger <shemming@brocade.com>
Cc: netdev@vger.kernel.org
Subject: [iproute PATCH 1/6] iplink: List valid 'type' argument in ip link help text
Date: Sat, 9 Jul 2016 11:22:45 +0200 [thread overview]
Message-ID: <1468056170-6056-2-git-send-email-phil@nwl.cc> (raw)
In-Reply-To: <1468056170-6056-1-git-send-email-phil@nwl.cc>
Signed-off-by: Phil Sutter <phil@nwl.cc>
---
ip/iplink.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/ip/iplink.c b/ip/iplink.c
index f2a2e13cf0c5b..0e3cee6af8b6f 100644
--- a/ip/iplink.c
+++ b/ip/iplink.c
@@ -55,7 +55,9 @@ void iplink_usage(void)
fprintf(stderr, " type TYPE [ ARGS ]\n");
fprintf(stderr, " ip link delete { DEVICE | dev DEVICE | group DEVGROUP } type TYPE [ ARGS ]\n");
fprintf(stderr, "\n");
- fprintf(stderr, " ip link set { DEVICE | dev DEVICE | group DEVGROUP } [ { up | down } ]\n");
+ fprintf(stderr, " ip link set { DEVICE | dev DEVICE | group DEVGROUP }\n");
+ fprintf(stderr, " [ { up | down } ]\n");
+ fprintf(stderr, " [ type TYPE ARGS ]\n");
} else
fprintf(stderr, "Usage: ip link set DEVICE [ { up | down } ]\n");
--
2.8.2
next prev parent reply other threads:[~2016-07-09 9:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 9:22 [iproute PATCH 0/6] iplink: Improve documentation Phil Sutter
2016-07-09 9:22 ` Phil Sutter [this message]
2016-07-09 9:22 ` [iproute PATCH 2/6] iplink: bond_slave: Add missing help functions Phil Sutter
2016-07-09 9:22 ` [iproute PATCH 3/6] ip-link.8: Extend type list in synopsis Phil Sutter
2016-07-09 9:22 ` [iproute PATCH 4/6] ip-link.8: Place 'ip link set' warning more prominently Phil Sutter
2016-07-09 9:22 ` [iproute PATCH 5/6] ip-link.8: Add slave type option descriptions Phil Sutter
2016-07-09 9:22 ` [iproute PATCH 6/6] ip-link.8: Fix font choices Phil Sutter
2016-07-20 19:13 ` [iproute PATCH 0/6] iplink: Improve documentation Stephen Hemminger
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=1468056170-6056-2-git-send-email-phil@nwl.cc \
--to=phil@nwl.cc \
--cc=netdev@vger.kernel.org \
--cc=shemming@brocade.com \
/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).