From: Serhey Popovych <serhe.popovych@gmail.com>
To: netdev@vger.kernel.org
Subject: [PATCH iproute2 v3 0/7] ip6/tunnel: Unify tclass, flowlabel and encap_limit output
Date: Mon, 8 Jan 2018 19:04:25 +0200 [thread overview]
Message-ID: <1515431072-29128-1-git-send-email-serhe.popovych@gmail.com> (raw)
With this series I want to improve printing of tclass,
flowlabel and encapsulation limit (encap_limit) options.
Everything within this series is open for your comments,
suggestions and criticism.
See individual patch description message for details.
Thanks,
Serhii
Serhey Popovych (7):
ip6/tunnel: Fix tclass output
ip6tnl/tunnel: Do not print obscure flowinfo
ip6/tunnel: Unify tclass printing
ip6/tunnel: Unify flowlabel printing
ip6/tunnel: Unify encap_limit printing
gre6/tunnel: Output flowlabel after tclass
ip6tnl/tunnel: Output hoplimit before encapsulation limit
ip/link_gre6.c | 54 ++++++++++++++++------------------------------
ip/link_ip6tnl.c | 63 ++++++++++++++++++------------------------------------
2 files changed, 40 insertions(+), 77 deletions(-)
--
1.7.10.4
next reply other threads:[~2018-01-08 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 17:04 Serhey Popovych [this message]
2018-01-08 17:04 ` [PATCH iproute2 v3 1/7] ip6/tunnel: Fix tclass output Serhey Popovych
2018-01-08 17:04 ` [PATCH iproute2 v3 2/7] ip6tnl/tunnel: Do not print obscure flowinfo Serhey Popovych
2018-01-08 17:04 ` [PATCH iproute2 v3 3/7] ip6/tunnel: Unify tclass printing Serhey Popovych
2018-01-08 17:04 ` [PATCH iproute2 v3 4/7] ip6/tunnel: Unify flowlabel printing Serhey Popovych
2018-01-08 17:04 ` [PATCH iproute2 v3 5/7] ip6/tunnel: Unify encap_limit printing Serhey Popovych
2018-01-08 17:04 ` [PATCH iproute2 v3 6/7] gre6/tunnel: Output flowlabel after tclass Serhey Popovych
2018-01-08 17:07 ` [PATCH iproute2 v3 0/7] ip6/tunnel: Unify tclass, flowlabel and encap_limit output Serhey Popovych
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=1515431072-29128-1-git-send-email-serhe.popovych@gmail.com \
--to=serhe.popovych@gmail.com \
--cc=netdev@vger.kernel.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).