From: Phil Sutter <phil@nwl.cc>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: [iproute PATCH 04/10] man: devlink.8: Document -verbose option
Date: Thu, 16 Aug 2018 12:27:56 +0200 [thread overview]
Message-ID: <20180816102802.31782-5-phil@nwl.cc> (raw)
In-Reply-To: <20180816102802.31782-1-phil@nwl.cc>
This was the only bit missing in comparison to devlink help text.
Signed-off-by: Phil Sutter <phil@nwl.cc>
---
man/man8/devlink.8 | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/man/man8/devlink.8 b/man/man8/devlink.8
index ac61b6add7fba..360031f77c165 100644
--- a/man/man8/devlink.8
+++ b/man/man8/devlink.8
@@ -47,6 +47,10 @@ Generate JSON output.
.BR "\-p" , " --pretty"
When combined with -j generate a pretty JSON output.
+.TP
+.BR "\-v" , " --verbose"
+Turn on verbose output.
+
.SS
.I OBJECT
--
2.18.0
next prev parent reply other threads:[~2018-08-16 13:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 10:27 [iproute PATCH 00/10] Review help texts and man pages Phil Sutter
2018-08-16 10:27 ` [iproute PATCH 01/10] man: bridge.8: Document -oneline option Phil Sutter
2018-08-16 10:27 ` [iproute PATCH 02/10] bridge: trivial: Make help text consistent Phil Sutter
2018-08-16 10:27 ` [iproute PATCH 03/10] devlink: " Phil Sutter
2018-08-16 10:27 ` Phil Sutter [this message]
2018-08-16 10:27 ` [iproute PATCH 05/10] genl: Fix help text Phil Sutter
2018-08-16 10:27 ` [iproute PATCH 06/10] man: ifstat.8: Document --json and --pretty options Phil Sutter
2018-08-16 10:27 ` [iproute PATCH 07/10] ip: Add missing -M flag to help text Phil Sutter
2018-08-17 11:22 ` Phil Sutter
2018-08-16 10:28 ` [iproute PATCH 08/10] man: rtacct.8: Fix nstat options Phil Sutter
2018-08-16 10:28 ` [iproute PATCH 09/10] rtmon: List options in help text Phil Sutter
2018-08-16 10:28 ` [iproute PATCH 10/10] man: ss.8: Describe --events option Phil Sutter
2018-08-16 17:29 ` [iproute PATCH 00/10] Review help texts and man pages 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=20180816102802.31782-5-phil@nwl.cc \
--to=phil@nwl.cc \
--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;
as well as URLs for NNTP newsgroup(s).