From: Stephen Hemminger <stephen@networkplumber.org>
To: Serhey Popovych <serhe.popovych@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 0/7] ip6/tunnel: Unify tclass, flowlabel and encap_limit output
Date: Tue, 9 Jan 2018 08:12:37 -0800 [thread overview]
Message-ID: <20180109081237.38e6cd1b@xeon-e3> (raw)
In-Reply-To: <1515431198-29362-1-git-send-email-serhe.popovych@gmail.com>
On Mon, 8 Jan 2018 19:06:31 +0200
Serhey Popovych <serhe.popovych@gmail.com> wrote:
> 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(-)
>
I am confused. this patch series arrived after the v3 version.
Which one is correct?
Also when sending multiple versions of a patch series is it is
best practice to include a revision history in the cover letter like:
v2
ip6/tunnel - incorporate review feedback in fou
v3
ip/gre - fix spelling errors
next prev parent reply other threads:[~2018-01-09 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 17:06 [PATCH iproute2 0/7] ip6/tunnel: Unify tclass, flowlabel and encap_limit output Serhey Popovych
2018-01-08 17:06 ` [PATCH iproute2 1/7] ip6/tunnel: Fix tclass output Serhey Popovych
2018-01-08 17:06 ` [PATCH iproute2 2/7] ip6tnl/tunnel: Do not print obscure flowinfo Serhey Popovych
2018-01-08 17:06 ` [PATCH iproute2 3/7] ip6/tunnel: Unify tclass printing Serhey Popovych
2018-01-08 17:06 ` [PATCH iproute2 4/7] ip6/tunnel: Unify flowlabel printing Serhey Popovych
2018-01-08 17:06 ` [PATCH iproute2 5/7] ip6/tunnel: Unify encap_limit printing Serhey Popovych
2018-01-08 17:06 ` [PATCH iproute2 6/7] gre6/tunnel: Output flowlabel after tclass Serhey Popovych
2018-01-08 17:06 ` [PATCH iproute2 7/7] ip6tnl/tunnel: Output hoplimit before encapsulation limit Serhey Popovych
2018-01-09 16:12 ` Stephen Hemminger [this message]
2018-01-10 15:35 ` [PATCH iproute2 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=20180109081237.38e6cd1b@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=serhe.popovych@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 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).