From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Aman Singh <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: <dev@dpdk.org>, Xiaoyun Li <xiaoyun.li@intel.com>, <skori@marvell.com>
Subject: Re: [PATCH v1 3/3] app/testpmd: support different input color method
Date: Fri, 20 May 2022 23:09:33 +0100 [thread overview]
Message-ID: <47dbd317-66ad-45f3-3fed-20326ef53502@amd.com> (raw)
In-Reply-To: <20220301090056.1042866-3-skori@marvell.com>
On 3/1/2022 9:00 AM, skori@marvell.com wrote:
> From: Sunil Kumar Kori <skori@marvell.com>
>
> Support for input coloring is added based on VLAN. Patch
> adds support for the same.
>
> Signed-off-by: Sunil Kumar Kori <skori@marvell.com>
Hi Aman, Yuying, Cristian,
Can you please review this patch?
For reference, patchwork link:
https://patches.dpdk.org/project/dpdk/patch/20220301090056.1042866-3-skori@marvell.com/
Thanks,
ferruh
<...>
next prev parent reply other threads:[~2022-05-20 22:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 9:00 [PATCH v1 1/3] common/cnxk: update precolor table setup for VLAN skori
2022-03-01 9:00 ` [PATCH v1 2/3] net/cnxk: support ops to update precolor VLAN table skori
2022-06-16 9:48 ` [PATCH v2 1/2] common/cnxk: update precolor table setup for VLAN skori
2022-06-16 9:48 ` [PATCH v2 2/2] net/cnxk: support ops to update precolor VLAN table skori
2022-06-16 11:54 ` [PATCH v3 1/2] common/cnxk: update precolor table setup for VLAN skori
2022-06-16 11:54 ` [PATCH v3 2/2] net/cnxk: support ops to update precolor VLAN table skori
2022-06-20 17:44 ` Jerin Jacob
2022-06-21 7:19 ` [EXT] " Sunil Kumar Kori
2022-06-21 7:35 ` [PATCH v4 1/2] common/cnxk: update precolor table setup for VLAN skori
2022-06-21 7:35 ` [PATCH v4 2/2] net/cnxk: support ops to update precolor VLAN table skori
2022-08-22 12:33 ` Jerin Jacob
2022-03-01 9:00 ` [PATCH v1 3/3] app/testpmd: support different input color method skori
2022-05-20 22:09 ` Ferruh Yigit [this message]
2022-05-21 7:07 ` [EXT] " Sunil Kumar Kori
2022-05-23 8:43 ` Ferruh Yigit
2022-05-24 7:35 ` [PATCH v2 1/1] " skori
2022-05-25 12:36 ` Dumitrescu, Cristian
2022-05-25 14:32 ` Sunil Kumar Kori
2022-05-25 14:37 ` skori
2022-05-25 14:41 ` Dumitrescu, Cristian
2022-05-31 15:41 ` Andrew Rybchenko
2022-06-03 13:03 ` [EXT] " Sunil Kumar Kori
2022-06-03 13:06 ` [PATCH v3 " skori
2022-06-08 12:06 ` Andrew Rybchenko
2022-06-14 10:05 ` [PATCH v4 " skori
2022-06-23 11:05 ` Andrew Rybchenko
2022-06-23 12:54 ` [EXT] " Sunil Kumar Kori
2022-06-23 12:57 ` [PATCH v5 " skori
2022-06-23 13:07 ` Sunil Kumar Kori
2022-06-24 12:44 ` Andrew Rybchenko
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=47dbd317-66ad-45f3-3fed-20326ef53502@amd.com \
--to=ferruh.yigit@amd.com \
--cc=aman.deep.singh@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=skori@marvell.com \
--cc=xiaoyun.li@intel.com \
--cc=yuying.zhang@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).