From: Serhey Popovych <serhe.popovych@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 0/7] ip6/tunnel: Unify tclass, flowlabel and encap_limit output
Date: Wed, 10 Jan 2018 17:35:50 +0200 [thread overview]
Message-ID: <e1d61e39-7bc7-8968-0d90-65c62143c642@gmail.com> (raw)
In-Reply-To: <20180109081237.38e6cd1b@xeon-e3>
[-- Attachment #1.1: Type: text/plain, Size: 1427 bytes --]
Stephen Hemminger wrote:
> 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
>
>
Ah, sorry for that inconvenience. Addressed with v4.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2018-01-10 15:35 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 ` [PATCH iproute2 0/7] ip6/tunnel: Unify tclass, flowlabel and encap_limit output Stephen Hemminger
2018-01-10 15:35 ` Serhey Popovych [this message]
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=e1d61e39-7bc7-8968-0d90-65c62143c642@gmail.com \
--to=serhe.popovych@gmail.com \
--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 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.