From: John Daley <johndale@cisco.com>
To: ferruh.yigit@intel.com
Cc: dev@dpdk.org, John Daley <johndale@cisco.com>
Subject: [dpdk-dev] [PATCH v2] enic flow director fixes
Date: Wed, 8 Feb 2017 16:40:08 -0800 [thread overview]
Message-ID: <20170209004009.26242-1-johndale@cisco.com> (raw)
In-Reply-To: <20170203095446.4614-1-johndale@cisco.com>
This should replace
http://www.dpdk.org/dev/patchwork/patch/20147/ which was an intermediate patch
in a small patchset and had a compile error. Also, please reject the 2nd patch
in the patchset http://www.dpdk.org/dev/patchwork/patch/20148/ which is
incomplete. I will change the state of these patches in patchworks.
thank you, john
John Daley (1):
net/enic: fix hardcoding of some flow director masks
drivers/net/enic/enic_clsf.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
--
2.10.0
next prev parent reply other threads:[~2017-02-09 0:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 9:54 [dpdk-dev] [PATCH 1/2] net/enic: fix hardcoding of some flow director masks John Daley
2017-02-03 9:54 ` [dpdk-dev] [PATCH 2/2] net/enic: fix flow director IPv6 traffic class specification John Daley
2017-02-03 22:54 ` [dpdk-dev] [PATCH 1/2] net/enic: fix hardcoding of some flow director masks Ferruh Yigit
2017-02-09 0:40 ` John Daley [this message]
2017-02-09 0:40 ` [dpdk-dev] [PATCH v2] " John Daley
2017-02-09 10:16 ` Ferruh Yigit
2017-02-09 17:43 ` John Daley (johndale)
2017-02-09 17:58 ` Ferruh Yigit
2017-02-09 12:21 ` Ferruh Yigit
2017-02-09 12:15 ` [dpdk-dev] [PATCH v2] enic flow director fixes Ferruh Yigit
2017-02-09 17:44 ` John Daley (johndale)
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=20170209004009.26242-1-johndale@cisco.com \
--to=johndale@cisco.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).