From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
Jeff Guo <jia.guo@intel.com>, Haiyue Wang <haiyue.wang@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/3] ethdev: remove L2 tunnel config API
Date: Thu, 29 Oct 2020 22:49:52 +0000 [thread overview]
Message-ID: <264b73fc-38b8-5ae1-f62f-04c946d91afd@intel.com> (raw)
In-Reply-To: <1603361181-21556-1-git-send-email-arybchenko@solarflare.com>
On 10/22/2020 11:06 AM, Andrew Rybchenko wrote:
> Dispite of the deprecation notice I'm not 100% sure that corresponding
> functionality is supported via flow API. Since the functionality is
> supported by the net/ixgbe driver only, it is a question to maintainers.
>
> The patch series should be applied on top of [1].
>
> [1] https://patches.dpdk.org/project/dpdk/list/?series=13207
>
> Andrew Rybchenko (3):
> ethdev: remove API to config L2 tunnel EtherType
> ethdev: remove L2 tunnel offload control API
> ethdev: move L2 tunnel config structure to ixgbe driver
>
for series,
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2020-10-29 22:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 10:06 Andrew Rybchenko
2020-10-22 10:06 ` [dpdk-dev] [PATCH 1/3] ethdev: remove API to config L2 tunnel EtherType Andrew Rybchenko
2020-10-23 2:09 ` Wang, Haiyue
2020-10-23 3:07 ` Guo, Jia
2020-10-22 10:06 ` [dpdk-dev] [PATCH 2/3] ethdev: remove L2 tunnel offload control API Andrew Rybchenko
2020-10-23 2:11 ` Wang, Haiyue
2020-10-23 3:07 ` Guo, Jia
2020-10-22 10:06 ` [dpdk-dev] [PATCH 3/3] ethdev: move L2 tunnel config structure to ixgbe driver Andrew Rybchenko
2020-10-23 2:12 ` Wang, Haiyue
2020-10-23 3:10 ` Guo, Jia
2020-10-29 22:49 ` 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=264b73fc-38b8-5ae1-f62f-04c946d91afd@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=jia.guo@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).