All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Cree <ecree@solarflare.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: <netdev@vger.kernel.org>
Subject: [PATCH v2 ethtool 0/2] IPv6 RXNFC
Date: Thu, 17 Mar 2016 19:09:10 +0000	[thread overview]
Message-ID: <56EB00D6.3060003@solarflare.com> (raw)

This series adds support for steering of IPv6 receive flows.

Changes since v1:
* Fixed and simplified IPv6 address and mask parsing
* Made help text / man page more consistent
* Dropped ethtool-copy.h patch as upstream is now newer

Edward Cree (2):
  Add IPv6 support to NFC
  Documentation for IPv6 NFC

 ethtool.8.in |  29 +++++--
 ethtool.c    |  25 +++++-
 rxclass.c    | 268 +++++++++++++++++++++++++++++++++++++++++++++++++++++++----
 3 files changed, 298 insertions(+), 24 deletions(-)

             reply	other threads:[~2016-03-17 19:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17 19:09 Edward Cree [this message]
2016-03-17 19:17 ` [PATCH v2 ethtool 1/2] Add IPv6 support to NFC Edward Cree
2016-03-17 19:17 ` [PATCH v2 ethtool 2/2] Documentation for IPv6 NFC Edward Cree
2016-04-22 13:41 ` [PATCH v2 ethtool 0/2] IPv6 RXNFC Edward Cree
2016-06-25 23:18 ` Ben Hutchings

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=56EB00D6.3060003@solarflare.com \
    --to=ecree@solarflare.com \
    --cc=ben@decadent.org.uk \
    --cc=netdev@vger.kernel.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.