From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Hyong Youb Kim <hyonkim@cisco.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/6] net/enic: minor updates to flow implementation
Date: Mon, 21 Sep 2020 17:12:36 +0100 [thread overview]
Message-ID: <a30b4ac7-2de1-4a86-0884-6f8bf2bbb75b@intel.com> (raw)
In-Reply-To: <20200909140006.23788-1-hyonkim@cisco.com>
On 9/9/2020 3:00 PM, Hyong Youb Kim wrote:
> This series enables several flow features such as priorities and
> egress PORT_ID action. It depends on the ealier patch series that adds
> VF representors.
>
> The 1st patch (remove obsolete code) does not technically belong in
> the series, but is piggybacked here as it is a trivial cleanup.
>
> Thanks..
> -Hyong
>
>
> Hyong Youb Kim (6):
> net/enic: remove obsolete code
> net/enic: support egress PORT_ID action
> net/enic: support priorities for TCAM flows
> net/enic: ignore vlan inner type when it is zero
> net/enic: generate VXLAN source port if it is zero in template
> net/enic: support VXLAN decap action combined with VLAN pop
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2020-09-21 16:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 14:00 Hyong Youb Kim
2020-09-09 14:00 ` [dpdk-dev] [PATCH 1/6] net/enic: remove obsolete code Hyong Youb Kim
2020-09-09 14:00 ` [dpdk-dev] [PATCH 2/6] net/enic: support egress PORT_ID action Hyong Youb Kim
2020-09-09 14:00 ` [dpdk-dev] [PATCH 3/6] net/enic: support priorities for TCAM flows Hyong Youb Kim
2020-09-09 14:00 ` [dpdk-dev] [PATCH 4/6] net/enic: ignore vlan inner type when it is zero Hyong Youb Kim
2020-09-09 14:00 ` [dpdk-dev] [PATCH 5/6] net/enic: generate VXLAN source port if it is zero in template Hyong Youb Kim
2020-09-09 14:00 ` [dpdk-dev] [PATCH 6/6] net/enic: support VXLAN decap action combined with VLAN pop Hyong Youb Kim
2020-09-21 16: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=a30b4ac7-2de1-4a86-0884-6f8bf2bbb75b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=hyonkim@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 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).