From: Serhey Popovych <serhe.popovych@gmail.com>
To: netdev@vger.kernel.org
Cc: jbenc@redhat.com, u9012063@gmail.com, julien@cumulusnetworks.com
Subject: [PATCH iproute2-next 0/2] ip/tunnel: Unify collect metadata handling
Date: Mon, 22 Jan 2018 18:46:52 +0200 [thread overview]
Message-ID: <1516639614-12960-1-git-send-email-serhe.popovych@gmail.com> (raw)
With this series I want to unify collect metadata
handling in tunnels:
1) Use "collect_metadata" name for JSON and
"external" keyword for non-JSON printing.
Do not *print* any options when tunnel in
collect metadata mode: gre6 already do
this, so just apply to others.
2) Do not *add* any attributes when configuring
gre tunnel in collect metadata mode.
Other tunnels (e.g. gre6, iptnl, ip6tnl)
alredy do that.
This is next step in ipv4 and ipv6 modules
unification to prepare for merge in the future.
Any comments, suggestions and criticism as always
welcome.
Thanks,
Serhii
Serhey Popovych (2):
ip/tunnel: Be consistent when printing tunnel collect metadata
gre/gre6: Unify attribute addition to netlink buffer
ip/link_gre.c | 50 ++++++++++++++++++++++++--------------------------
ip/link_gre6.c | 13 ++++++++-----
ip/link_ip6tnl.c | 6 ++++--
ip/link_iptnl.c | 6 ++++--
4 files changed, 40 insertions(+), 35 deletions(-)
--
1.7.10.4
next reply other threads:[~2018-01-22 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 16:46 Serhey Popovych [this message]
2018-01-22 16:46 ` [PATCH iproute2-next 1/2] ip/tunnel: Be consistent when printing tunnel collect metadata Serhey Popovych
2018-01-22 16:58 ` Jiri Benc
2018-01-22 17:00 ` Serhey Popovych
2018-01-22 16:46 ` [PATCH iproute2-next 2/2] gre/gre6: Unify attribute addition to netlink buffer 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=1516639614-12960-1-git-send-email-serhe.popovych@gmail.com \
--to=serhe.popovych@gmail.com \
--cc=jbenc@redhat.com \
--cc=julien@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=u9012063@gmail.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 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.