From: David Lebrun <david.lebrun@uclouvain.be>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH iproute2 net-next 2/3] iproute: add support for SRv6 local segment processing
Date: Wed, 9 Aug 2017 16:53:42 +0200 [thread overview]
Message-ID: <6b7a01fc-fe10-cc5f-d54a-2da3b9b47ae9@uclouvain.be> (raw)
In-Reply-To: <20170809074316.3acaafa1@xeon-e3>
[-- Attachment #1.1: Type: text/plain, Size: 136 bytes --]
On 08/09/2017 04:43 PM, Stephen Hemminger wrote:
> Why is this not a table instead of code?
Fair point, will send a v2.
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2017-08-09 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 13:16 [PATCH iproute2 net-next 0/3] Add support for SRv6 local segment processing David Lebrun
2017-08-09 13:16 ` [PATCH iproute2 net-next 1/3] iproute: add helper functions for SRH processing David Lebrun
2017-08-09 13:17 ` [PATCH iproute2 net-next 2/3] iproute: add support for SRv6 local segment processing David Lebrun
2017-08-09 14:43 ` Stephen Hemminger
2017-08-09 14:53 ` David Lebrun [this message]
2017-08-09 13:17 ` [PATCH iproute2 net-next 3/3] man: add documentation for seg6local lwt David Lebrun
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=6b7a01fc-fe10-cc5f-d54a-2da3b9b47ae9@uclouvain.be \
--to=david.lebrun@uclouvain.be \
--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 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).