From: Edward Cree <ecree@solarflare•com>
To: Ben Hutchings <ben@decadent•org.uk>
Cc: <netdev@vger•kernel.org>
Subject: Re: [PATCH ethtool 3/3] Documentation for IPv6 NFC
Date: Wed, 16 Mar 2016 14:54:07 +0000 [thread overview]
Message-ID: <56E9738F.3080204@solarflare.com> (raw)
In-Reply-To: <1457887638.3331.33.camel@decadent.org.uk>
On 13/03/16 16:47, Ben Hutchings wrote:
> Why is ip6 added in the middle of the IPv4 flow-types here...
> ...and here...
> ...but not here?
Good catch; I will make them all like the last one.
> Missing nexthdr?
On the contrary, it needed to be removed from all the other places - there
is no nexthdr input, only l4proto.
-Ed
prev parent reply other threads:[~2016-03-16 15:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 14:56 [PATCH ethtool 0/3] IPv6 RXNFC Edward Cree
2016-02-15 14:59 ` [PATCH ethtool 1/3] ethtool-copy.h: sync with net-next Edward Cree
2016-02-15 14:59 ` [PATCH ethtool 2/3] Add IPv6 support to NFC Edward Cree
2016-03-13 16:43 ` Ben Hutchings
2016-03-16 14:53 ` Edward Cree
2016-03-16 17:15 ` Ben Hutchings
2016-02-15 15:00 ` [PATCH ethtool 3/3] Documentation for IPv6 NFC Edward Cree
2016-03-13 16:47 ` Ben Hutchings
2016-03-16 14:54 ` Edward Cree [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=56E9738F.3080204@solarflare.com \
--to=ecree@solarflare$(echo .)com \
--cc=ben@decadent$(echo .)org.uk \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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