DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pascal Mazon <pascal.mazon@6wind.com>
To: keith.wiles@intel.com
Cc: dev@dpdk.org, Pascal Mazon <pascal.mazon@6wind.com>
Subject: [dpdk-dev] [PATCH v3 0/3] net/tap: netlink and MAC address fixes
Date: Fri, 31 Mar 2017 15:54:08 +0200	[thread overview]
Message-ID: <cover.1490966849.git.pascal.mazon@6wind.com> (raw)
In-Reply-To: <3f667d40be2f2d4db572bfa4200561e5818514b6.1490965230.git.pascal.mazon@6wind.com>

I'm adding a cover letter to clarify this series history, as I've mixed my
versions a little...

This series fixes some errors in the tap PMD.

v3 changes:
  - Re-sending the complete patch series:
      [PATCH v3 1/3] net/tap: update netlink error code management
      [PATCH v3 2/3] net/tap: fix null MAC address at init
      [PATCH v3 3/3] net/tap: fix redirection rule after MAC change


v2 changes:
  I separated patch for MAC address in two:
  - 1 for ensuring the device MAC address is set immediately after init:
      [PATCH v2 1/2] net/tap: fix null MAC address at init

  - 1 for ensuring the MAC address redirection rule is changed when
    needed:
      [PATCH v2 2/2] net/tap: fix redirection rule after MAC change

  But I forgot to re-send the netlink patch, which is now missing from
  DPDK patchwork...

v1:
  - 1 patch for netlink: correctly interpret the kernel's error message:
      [PATCH 1/2] net/tap: update netlink error code management

  - 1 patch for MAC address: update remote MAC address redirection:
      [PATCH 2/2] net/tap: update redirection rule after MAC change

Pascal Mazon (3):
  net/tap: update netlink error code management
  net/tap: fix null MAC address at init
  net/tap: fix redirection rule after MAC change

 drivers/net/tap/rte_eth_tap.c | 108 +++++++++++++++++++++++++++---------------
 drivers/net/tap/tap_flow.c    |  22 ++++++++-
 drivers/net/tap/tap_netlink.c |  73 +++++++++++++---------------
 drivers/net/tap/tap_tcmsgs.c  | 107 ++++++++++-------------------------------
 drivers/net/tap/tap_tcmsgs.h  |   2 -
 5 files changed, 151 insertions(+), 161 deletions(-)

--
2.12.0.306.g4a9b9b3

  reply	other threads:[~2017-03-31 13:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29  9:44 [dpdk-dev] [PATCH 1/2] net/tap: update netlink error code management Pascal Mazon
2017-03-29  9:44 ` [dpdk-dev] [PATCH 2/2] net/tap: update redirection rule after MAC change Pascal Mazon
2017-03-31 13:02   ` [dpdk-dev] [PATCH v2 1/2] net/tap: fix null MAC address at init Pascal Mazon
2017-03-31 13:54     ` Pascal Mazon [this message]
2017-03-31 13:54       ` [dpdk-dev] [PATCH v3 1/3] net/tap: update netlink error code management Pascal Mazon
2017-03-31 13:54       ` [dpdk-dev] [PATCH v3 2/3] net/tap: fix null MAC address at init Pascal Mazon
2017-03-31 13:54       ` [dpdk-dev] [PATCH v3 3/3] net/tap: fix redirection rule after MAC change Pascal Mazon
2017-04-03 13:11       ` [dpdk-dev] [PATCH v3 0/3] net/tap: netlink and MAC address fixes Ferruh Yigit
2017-03-31 13:02   ` [dpdk-dev] [PATCH v2 2/2] net/tap: fix redirection rule after MAC change Pascal Mazon

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=cover.1490966849.git.pascal.mazon@6wind.com \
    --to=pascal.mazon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.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 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).