From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John Daley <johndale@cisco.com>
Cc: dev@dpdk.org, adrien.mazarguil@6wind.com
Subject: Re: [PATCH 1/6] net/enic: bring NIC interface functions up to date
Date: Fri, 31 Mar 2017 11:12:28 +0100 [thread overview]
Message-ID: <0856cbff-e84b-5345-cb96-00de9bfe7020@intel.com> (raw)
In-Reply-To: <20170330212838.31291-1-johndale@cisco.com>
On 3/30/2017 10:28 PM, John Daley wrote:
> Update the base functions for the Cisco VIC. These files are mostly
> common with other VIC drivers so are left alone is as much as possilbe.
> Includes in a new filter/action interface which is needed for Generic
> Flow API PMD support. Update FDIR code to use the new interface.
>
> Signed-off-by: John Daley <johndale@cisco.com>
Hi John,
Patchset is a little late for this release (17.05), and will be
considered for next release (17.08).
Thanks,
ferruh
prev parent reply other threads:[~2017-03-31 10:12 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 21:28 [PATCH 1/6] net/enic: bring NIC interface functions up to date John Daley
2017-03-30 21:28 ` [PATCH 2/6] net/enic: flow API skeleton John Daley
2017-03-30 21:28 ` [PATCH 3/6] net/enic: flow API for NICs with advanced filters enabled John Daley
2017-03-30 21:28 ` [PATCH 4/6] net/enic: flow API for NICs with advanced filters disabled John Daley
2017-03-30 21:28 ` [PATCH 5/6] net/enic: flow API support for Legacy NICs John Daley
2017-03-30 21:28 ` [PATCH 6/6] net/enic: flow API debug John Daley
2017-03-31 2:06 ` [PATCH v2 0/7] *** flow API support for enic *** John Daley
2017-03-31 2:06 ` [PATCH v2 1/7] net/enic: bring NIC interface functions up to date John Daley
2017-03-31 2:06 ` [PATCH v2 2/7] net/enic: flow API skeleton John Daley
2017-03-31 2:06 ` [PATCH v2 3/7] net/enic: flow API for NICs with advanced filters enabled John Daley
2017-03-31 2:06 ` [PATCH v2 4/7] net/enic: flow API for NICs with advanced filters disabled John Daley
2017-03-31 2:06 ` [PATCH v2 5/7] net/enic: flow API for Legacy NICs John Daley
2017-03-31 2:06 ` [PATCH v2 6/7] net/enic: flow API debug John Daley
2017-03-31 2:06 ` [PATCH v2 7/7] net/enic: flow API documentation John Daley
2017-04-02 15:18 ` Mcnamara, John
2017-05-12 12:11 ` Ferruh Yigit
2017-05-17 3:03 ` [PATCH v3 0/6] enic flow api support John Daley
2017-05-17 3:03 ` [PATCH v3 1/6] net/enic: flow API skeleton John Daley
2017-05-17 11:12 ` Ferruh Yigit
2017-05-17 3:03 ` [PATCH v3 2/6] net/enic: flow API for NICs with advanced filters enabled John Daley
2017-05-17 11:12 ` Ferruh Yigit
2017-05-17 3:03 ` [PATCH v3 3/6] net/enic: flow API for NICs with advanced filters disabled John Daley
2017-05-17 11:13 ` Ferruh Yigit
2017-05-17 3:03 ` [PATCH v3 4/6] net/enic: flow API for Legacy NICs John Daley
2017-05-17 3:03 ` [PATCH v3 5/6] net/enic: flow API debug John Daley
2017-05-17 3:03 ` [PATCH v3 6/6] net/enic: flow API documentation John Daley
2017-05-17 11:13 ` Ferruh Yigit
2017-05-17 22:38 ` [PATCH v4 0/8] enic flow api support John Daley
2017-05-17 22:38 ` [PATCH v4 1/8] net/enic: bring NIC interface functions up to date John Daley
2017-05-22 9:49 ` Ferruh Yigit
2017-06-08 10:44 ` Jerin Jacob
2017-05-17 22:38 ` [PATCH v4 2/8] net/enic: flow API skeleton John Daley
2017-05-17 22:38 ` [PATCH v4 3/8] net/enic: flow API for NICs with advanced filters enabled John Daley
2017-05-17 22:38 ` [PATCH v4 4/8] net/enic: flow API mark and flag support John Daley
2017-05-17 22:38 ` [PATCH v4 5/8] net/enic: flow API for NICs with advanced filters disabled John Daley
2017-05-17 22:38 ` [PATCH v4 6/8] net/enic: flow API for Legacy NICs John Daley
2017-05-17 22:38 ` [PATCH v4 7/8] net/enic: flow API debug John Daley
2017-05-17 22:38 ` [PATCH v4 8/8] net/enic: flow API documentation John Daley
2017-05-22 10:05 ` [PATCH v4 0/8] enic flow api support Ferruh Yigit
2017-05-17 11:12 ` [PATCH v3 0/6] " Ferruh Yigit
2017-03-31 10:12 ` Ferruh Yigit [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=0856cbff-e84b-5345-cb96-00de9bfe7020@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=johndale@cisco.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 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.