From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com
Subject: Re: [PATCH 0/8] Add the features for nfp include VLAN strip, QinQ strip, VLAN insert
Date: Tue, 24 Jan 2023 16:28:18 +0000 [thread overview]
Message-ID: <59c712ca-6daf-cade-0655-b9070c655125@amd.com> (raw)
In-Reply-To: <20221128065359.12737-1-chaoyong.he@corigine.com>
On 11/28/2022 6:53 AM, Chaoyong He wrote:
> Add support for QinQ strip
> Add support for VLAN strip
> Add support for VLAN insert with NFD3
> Add support for VLAN insert with NFDk
>
> Peng Zhang (8):
> net/nfp: break out function to report device information
> net/nfp: modify the logic of parse metadata
> net/nfp: add new metadata type for achieving VLAN strip
> net/nfp: add support for QinQ strip
> net/nfp: add support for VLAN strip V2
> net/nfp: add support for VLAN insert with NFD3
> net/nfp: add support for VLAN insert V2 with NFD3
> net/nfp: add support for VLAN insert with NFDk
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-01-24 16:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 6:53 Chaoyong He
2022-11-28 6:53 ` [PATCH 1/8] net/nfp: break out function to report device information Chaoyong He
2023-01-16 2:24 ` Nole Zhang
2022-11-28 6:53 ` [PATCH 2/8] net/nfp: modify the logic of parse metadata Chaoyong He
2022-11-28 6:53 ` [PATCH 3/8] net/nfp: add new metadata type for achieving VLAN strip Chaoyong He
2022-11-28 6:53 ` [PATCH 4/8] net/nfp: add support for QinQ strip Chaoyong He
2022-11-28 6:53 ` [PATCH 5/8] net/nfp: add support for VLAN strip V2 Chaoyong He
2022-11-28 6:53 ` [PATCH 6/8] net/nfp: add support for VLAN insert with NFD3 Chaoyong He
2022-11-28 6:53 ` [PATCH 7/8] net/nfp: add support for VLAN insert V2 " Chaoyong He
2022-11-28 6:53 ` [PATCH 8/8] net/nfp: add support for VLAN insert with NFDk Chaoyong He
2023-01-24 16:28 ` 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=59c712ca-6daf-cade-0655-b9070c655125@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.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).