DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Pascal Mazon <pascal.mazon@6wind.com>, keith.wiles@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 0/3] net/tap: netlink and MAC address fixes
Date: Mon, 3 Apr 2017 14:11:37 +0100	[thread overview]
Message-ID: <f22848d6-3e67-39a9-c52b-c043254dea8f@intel.com> (raw)
In-Reply-To: <cover.1490966849.git.pascal.mazon@6wind.com>

On 3/31/2017 2:54 PM, Pascal Mazon wrote:
> 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.
> 
<...>
> 
> 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

Series applied to dpdk-next-net/master, thanks.

  parent reply	other threads:[~2017-04-03 13:12 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     ` [dpdk-dev] [PATCH v3 0/3] net/tap: netlink and MAC address fixes Pascal Mazon
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       ` Ferruh Yigit [this message]
2017-03-31 13:02   ` [dpdk-dev] [PATCH v2 2/2] " 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=f22848d6-3e67-39a9-c52b-c043254dea8f@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.com \
    --cc=pascal.mazon@6wind.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).