From: Hyong Youb Kim <hyonkim@cisco.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Hyong Youb Kim <hyonkim@cisco.com>
Subject: [dpdk-dev] [PATCH 0/2] net/enic: minor flow manager changes
Date: Thu, 2 Jul 2020 19:23:49 -0700 [thread overview]
Message-ID: <20200703022351.17172-1-hyonkim@cisco.com> (raw)
This series enables VLAN push/pop actions. The first patch adds code
to translate rte_flow push/pop actions to flow manager actions. The
second patch extends the debug-print function to print recently added
flow manager actions, including the ones used by the first patch.
Thanks.
-Hyong
Hyong Youb Kim (2):
net/enic: support VLAN push and pop flow actions
net/enic: add new flow manager actions to the dump function
doc/guides/rel_notes/release_20_08.rst | 3 ++
drivers/net/enic/enic_fm_flow.c | 68 ++++++++++++++++++++++++++
2 files changed, 71 insertions(+)
--
2.26.2
next reply other threads:[~2020-07-03 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 2:23 Hyong Youb Kim [this message]
2020-07-03 2:23 ` [dpdk-dev] [PATCH 1/2] net/enic: support VLAN push and pop flow actions Hyong Youb Kim
2020-07-03 2:23 ` [dpdk-dev] [PATCH 2/2] net/enic: add new flow manager actions to the dump function Hyong Youb Kim
2020-07-09 16:09 ` [dpdk-dev] [PATCH 0/2] net/enic: minor flow manager changes Ferruh Yigit
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=20200703022351.17172-1-hyonkim@cisco.com \
--to=hyonkim@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).