From: David Ahern <dsa@cumulusnetworks.com>
To: Robert Shearman <rshearma@brocade.com>, netdev@vger.kernel.org
Cc: stephen@networkplumber.org
Subject: Re: [PATCH v2 iproute2 net-next 2/2] iproute: Add support for MPLS LWT ttl attribute
Date: Tue, 11 Apr 2017 16:37:17 -0600 [thread overview]
Message-ID: <452878bb-36e4-e336-2182-8aa4dfd24c53@cumulusnetworks.com> (raw)
In-Reply-To: <1491899841-1361-3-git-send-email-rshearma@brocade.com>
On 4/11/17 2:37 AM, Robert Shearman wrote:
> Add support for setting and displaying the ttl attribute
> for MPLS IP lighweight tunnels.
>
> Signed-off-by: Robert Shearman <rshearma@brocade.com>
> ---
> ip/iproute_lwtunnel.c | 31 +++++++++++++++++++++++++++++--
> man/man8/ip-route.8.in | 9 ++++++++-
> 2 files changed, 37 insertions(+), 3 deletions(-)
>
Acked-by: David Ahern <dsa@cumulusnetworks.com>
next prev parent reply other threads:[~2017-04-11 22:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 14:36 [PATCH iproute2 net-next 0/2] ip: Allow TTL propagation to/from IP packets to be configured Robert Shearman
2017-04-10 14:36 ` [PATCH iproute2 net-next 1/2] iproute: Add support for ttl-propagation attribute Robert Shearman
2017-04-11 3:43 ` David Ahern
2017-04-11 8:35 ` Robert Shearman
2017-04-10 14:36 ` [PATCH iproute2 net-next 2/2] iproute: Add support for MPLS LWT ttl attribute Robert Shearman
2017-04-11 8:37 ` [PATCH v2 iproute2 net-next 0/2] ip: Allow TTL propagation to/from IP packets to be configured Robert Shearman
2017-04-11 8:37 ` [PATCH v2 iproute2 net-next 1/2] iproute: Add support for ttl-propagation attribute Robert Shearman
2017-04-11 22:37 ` David Ahern
2017-04-11 8:37 ` [PATCH v2 iproute2 net-next 2/2] iproute: Add support for MPLS LWT ttl attribute Robert Shearman
2017-04-11 22:37 ` David Ahern [this message]
2017-04-12 17:00 ` [PATCH iproute2 net-next 0/2] ip: Allow TTL propagation to/from IP packets to be configured Stephen Hemminger
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=452878bb-36e4-e336-2182-8aa4dfd24c53@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=rshearma@brocade.com \
--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.