From: Richard Alpe <richard.alpe@ericsson.com>
To: <netdev@vger.kernel.org>
Cc: tipc-discussion@lists.sourceforge.net
Subject: [PATCH iproute2 1/2] tipc: fix UDP bearer synopsis
Date: Tue, 9 Aug 2016 10:34:29 +0200 [thread overview]
Message-ID: <1470731670-12723-1-git-send-email-richard.alpe@ericsson.com> (raw)
Local ip is not required to identify a UDP bearer and shouldn't be
passed to bearer disable, set or get. In this patch we remove the
localip entry from the synopsis of these functions.
Signed-off-by: Richard Alpe <richard.alpe@ericsson.com>
---
man/man8/tipc-bearer.8 | 14 ++++----------
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/man/man8/tipc-bearer.8 b/man/man8/tipc-bearer.8
index 50a1ed2..846f1db 100644
--- a/man/man8/tipc-bearer.8
+++ b/man/man8/tipc-bearer.8
@@ -39,14 +39,12 @@ tipc-bearer \- show or modify TIPC bearers
.B tipc bearer disable media
.br
.RB "{ { " eth " | " ib " } " device
-.IR DEVICE
+.IR "DEVICE " }
.RB "|"
.br
.RB "{ " udp
.B name
-.IR NAME
-.B localip
-.IR LOCALIP " } }"
+.IR NAME " }"
.br
.ti -8
@@ -65,9 +63,7 @@ tipc-bearer \- show or modify TIPC bearers
.br
.RB "{ " udp
.B name
-.IR NAME
-.B localip
-.IR LOCALIP " } }"
+.IR NAME " }"
.br
.ti -8
@@ -80,9 +76,7 @@ tipc-bearer \- show or modify TIPC bearers
.br
.RB "{ " udp
.B name
-.IR NAME
-.B localip
-.IR LOCALIP " } }"
+.IR NAME " }"
.br
.ti -8
--
2.1.4
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
next reply other threads:[~2016-08-09 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 8:34 Richard Alpe [this message]
2016-08-09 8:34 ` [PATCH iproute2 2/2] tipc: refactor bearer identification Richard Alpe
2016-08-12 19:54 ` 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=1470731670-12723-1-git-send-email-richard.alpe@ericsson.com \
--to=richard.alpe@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
/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).