All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Serhey Popovych <serhe.popovych@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 v5 0/7] ip6/tunnel: Unify tclass, flowlabel and encap_limit output
Date: Wed, 10 Jan 2018 08:08:43 -0800	[thread overview]
Message-ID: <20180110080843.25b9bb3a@xeon-e3> (raw)
In-Reply-To: <1515599595-27958-1-git-send-email-serhe.popovych@gmail.com>

On Wed, 10 Jan 2018 17:53:08 +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.
> 
> v5
>   fix wrong cover letter subject and body
> 
> v4
>   rebased to current upstream
> 
> v1..v3
>   no changes. initially started with v3 instead of v1
> 
> 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(-)
> 


Applied, thanks for keeping going.

      parent reply	other threads:[~2018-01-10 16:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 15:53 [PATCH iproute2 v5 0/7] ip6/tunnel: Unify tclass, flowlabel and encap_limit output Serhey Popovych
2018-01-10 15:53 ` [PATCH iproute2 v5 1/7] ip6/tunnel: Fix tclass output Serhey Popovych
2018-01-10 15:53 ` [PATCH iproute2 v5 2/7] ip6tnl/tunnel: Do not print obscure flowinfo Serhey Popovych
2018-01-10 15:53 ` [PATCH iproute2 v5 3/7] ip6/tunnel: Unify tclass printing Serhey Popovych
2018-01-10 15:53 ` [PATCH iproute2 v5 4/7] ip6/tunnel: Unify flowlabel printing Serhey Popovych
2018-01-10 15:53 ` [PATCH iproute2 v5 5/7] ip6/tunnel: Unify encap_limit printing Serhey Popovych
2018-01-10 15:53 ` [PATCH iproute2 v5 6/7] gre6/tunnel: Output flowlabel after tclass Serhey Popovych
2018-01-10 15:53 ` [PATCH iproute2 v5 7/7] ip6tnl/tunnel: Output hoplimit before encapsulation limit Serhey Popovych
2018-01-10 16:08 ` Stephen Hemminger [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=20180110080843.25b9bb3a@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 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.