From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Danylo Vodopianov <dvo-plv@napatech.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
"aman.deep.singh@intel.com" <aman.deep.singh@intel.com>,
"yuying.zhang@intel.com" <yuying.zhang@intel.com>,
Ori Kam <orika@nvidia.com>,
"mko-plv@napatech.com" <mko-plv@napatech.com>,
"ckm@napatech.com" <ckm@napatech.com>,
"sil-plv@napatech.com" <sil-plv@napatech.com>
Cc: Gregory Etelson <getelson@nvidia.com>,
Alexander Kozyrev <akozyrev@nvidia.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>
Subject: RE: [PATCH v2 0/2] Testpmd flow update/destroy fixes
Date: Mon, 18 Nov 2024 10:43:40 +0000 [thread overview]
Message-ID: <CH3PR12MB84608EF670F1F8BCC2BCDF0EA4272@CH3PR12MB8460.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20241118102528.1858308-1-dvo-plv@napatech.com>
Hi Danylo,
Could you please resend the v2 of the patchset? I'm not sure why, but for some reason the patches are missing in patchwork. I also cannot find them on http://inbox.dpdk.org/dev/
Best regards,
Dariusz Sosnowski
> -----Original Message-----
> From: Danylo Vodopianov <dvo-plv@napatech.com>
> Sent: Monday, November 18, 2024 11:25
> To: NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>;
> aman.deep.singh@intel.com; yuying.zhang@intel.com; Ori Kam
> <orika@nvidia.com>; mko-plv@napatech.com; ckm@napatech.com; Dariusz
> Sosnowski <dsosnowski@nvidia.com>; sil-plv@napatech.com
> Cc: Gregory Etelson <getelson@nvidia.com>; Alexander Kozyrev
> <akozyrev@nvidia.com>; dev@dpdk.org; stable@dpdk.org;
> ferruh.yigit@amd.com
> Subject: [PATCH v2 0/2] Testpmd flow update/destroy fixes
>
> External email: Use caution opening links or attachments
>
>
> These patches provide next fixes:
> 1. The testpmd command “flow update…“ provides a nullptr as the
> context variable.
> 2. Avoid removal of additional flows after requested number of flows has
> been already removed.
> v2:
> 1. Rephase commit messages.
> 2. Copy user_id to the flow list for flow_update command.
> 3. Enclose the case's body for flow_destroy command in braces.
>
> Danylo Vodopianov (2):
> app/testpmd: fix flow update
> app/testpmd: fix aged flow destroy
>
> app/test-pmd/config.c | 27 ++++++++++++++++++++++++---
> 1 file changed, 24 insertions(+), 3 deletions(-)
>
> --
> 2.43.5
>
> Disclaimer: This email and any files transmitted with it may contain
> confidential information intended for the addressee(s) only. The information is
> not to be surrendered or copied to unauthorized persons. If you have received
> this communication in error, please notify the sender immediately and delete
> this e-mail from your system.
next prev parent reply other threads:[~2024-11-18 10:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 15:00 [PATCH v1 " Danylo Vodopianov
2024-10-31 15:00 ` [PATCH v1 1/2] app/testpmd: fix flow update Danylo Vodopianov
2024-11-15 17:39 ` Dariusz Sosnowski
2024-10-31 15:00 ` [PATCH v1 2/2] app/testpmd: fix flow destroy Danylo Vodopianov
2024-11-15 17:40 ` Dariusz Sosnowski
2024-11-11 13:35 ` [PATCH v1 0/2] Testpmd flow update/destroy fixes Ferruh Yigit
2024-11-14 14:12 ` Serhii Iliushyk
2024-11-14 20:18 ` Thomas Monjalon
[not found] ` <20241118102528.1858308-1-dvo-plv@napatech.com>
[not found] ` <20241118102528.1858308-2-dvo-plv@napatech.com>
2024-11-18 10:38 ` [PATCH v2 1/2] app/testpmd: fix flow update Dariusz Sosnowski
2024-11-18 10:43 ` Dariusz Sosnowski [this message]
[not found] ` <PAWP190MB2160717526F6D67E34952D2E8B272@PAWP190MB2160.EURP190.PROD.OUTLOOK.COM>
2024-11-18 10:59 ` [PATCH v2 0/2] Testpmd flow update/destroy fixes Dariusz Sosnowski
2024-11-18 11:26 ` Danylo Vodopianov
2024-11-18 11:26 ` [PATCH v2 1/2] app/testpmd: fix flow update Danylo Vodopianov
2024-11-18 12:40 ` Dariusz Sosnowski
2024-11-18 11:26 ` [PATCH v2 2/2] app/testpmd: fix aged flow destroy Danylo Vodopianov
2024-11-18 13:37 ` Dariusz Sosnowski
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=CH3PR12MB84608EF670F1F8BCC2BCDF0EA4272@CH3PR12MB8460.namprd12.prod.outlook.com \
--to=dsosnowski@nvidia.com \
--cc=akozyrev@nvidia.com \
--cc=aman.deep.singh@intel.com \
--cc=ckm@napatech.com \
--cc=dev@dpdk.org \
--cc=dvo-plv@napatech.com \
--cc=ferruh.yigit@amd.com \
--cc=getelson@nvidia.com \
--cc=mko-plv@napatech.com \
--cc=orika@nvidia.com \
--cc=sil-plv@napatech.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--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).