patches for DPDK stable branches
 help / color / mirror / Atom feed
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>,
	Mykola Kostenok <mko-plv@napatech.com>,
	Christian Koue Muf <ckm@napatech.com>,
	Serhii Iliushyk <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:59:31 +0000	[thread overview]
Message-ID: <CH3PR12MB846024A7DBBA8999191849D4A4272@CH3PR12MB8460.namprd12.prod.outlook.com> (raw)
In-Reply-To: <PAWP190MB2160717526F6D67E34952D2E8B272@PAWP190MB2160.EURP190.PROD.OUTLOOK.COM>

It seems that you're not registered to stable mailing list.
Could you please register on that list and try again?
You can use this link to register: https://mails.dpdk.org/listinfo/stable

> From: Danylo Vodopianov <dvo-plv@napatech.com> 
> Sent: Monday, November 18, 2024 11:48
> To: Dariusz Sosnowski <dsosnowski@nvidia.com>; NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>; aman.deep.singh@intel.com; yuying.zhang@intel.com; Ori Kam <orika@nvidia.com>; Mykola Kostenok <mko-plv@napatech.com>; Christian Koue Muf <ckm@napatech.com>; Serhii Iliushyk <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: RE: [PATCH v2 0/2] Testpmd flow update/destroy fixes
> 
> External email: Use caution opening links or attachments 
> 
> Hi, Dariusz
> 
> I think the reason is that email:
> 
> 
> I also get it for v1. Maybe you could advise, to who to contact I should ?
> ________________________________________
> От: Dariusz Sosnowski <mailto:dsosnowski@nvidia.com>
> Отправлено: 18 ноября 2024 г. 12:43
> Кому: Danylo Vodopianov <mailto:dvo-plv@napatech.com>; NBU-Contact-Thomas Monjalon (EXTERNAL) <mailto:thomas@monjalon.net>; mailto:aman.deep.singh@intel.com <mailto:aman.deep.singh@intel.com>; mailto:yuying.zhang@intel.com <mailto:yuying.zhang@intel.com>; Ori Kam <mailto:orika@nvidia.com>; Mykola Kostenok <mailto:mko-plv@napatech.com>; Christian Koue Muf <mailto:ckm@napatech.com>; Serhii Iliushyk <mailto:sil-plv@napatech.com>
> Копия: Gregory Etelson <mailto:getelson@nvidia.com>; Alexander Kozyrev <mailto:akozyrev@nvidia.com>; mailto:dev@dpdk.org <mailto:dev@dpdk.org>; mailto:stable@dpdk.org <mailto:stable@dpdk.org>; mailto:ferruh.yigit@amd.com <mailto:ferruh.yigit@amd.com>
> Тема: RE: [PATCH v2 0/2] Testpmd flow update/destroy fixes 
>  
> 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 https://linkprotect.cudasvc.com/url?a=http%3a%2f%2finbox.dpdk.org%2fdev%2f&c=E,1,dcZxFWB-eo1ewbHY7A168mmU8SGWF_I8DZ4pWHzAoDaMq5fBfu4xHL1kYRZJjDsBCqtKWlkfnn7_fKtrD8shz7BfbAmgFnTgi61I6AAPFseq9ppG&typo=1
> 
> Best regards,
> Dariusz Sosnowski
> 
> > -----Original Message-----
> > From: Danylo Vodopianov <mailto:dvo-plv@napatech.com>
> > Sent: Monday, November 18, 2024 11:25
> > To: NBU-Contact-Thomas Monjalon (EXTERNAL) <mailto:thomas@monjalon.net>;
> > mailto:aman.deep.singh@intel.com; mailto:yuying.zhang@intel.com; Ori Kam
> > <mailto:orika@nvidia.com>; mailto:mko-plv@napatech.com; mailto:ckm@napatech.com; Dariusz
> > Sosnowski <mailto:dsosnowski@nvidia.com>; mailto:sil-plv@napatech.com
> > Cc: Gregory Etelson <mailto:getelson@nvidia.com>; Alexander Kozyrev
> > <mailto:akozyrev@nvidia.com>; mailto:dev@dpdk.org; mailto:stable@dpdk.org;
> > mailto: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.
> 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. 
>

  parent reply	other threads:[~2024-11-18 10:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241031150010.2991953-1-dvo-plv@napatech.com>
2024-11-18 10:25 ` Danylo Vodopianov
2024-11-18 10:25   ` [PATCH v2 1/2] app/testpmd: fix flow update Danylo Vodopianov
2024-11-18 10:38     ` Dariusz Sosnowski
2024-11-18 10:25   ` [PATCH v2 2/2] app/testpmd: fix aged flow destroy Danylo Vodopianov
2024-11-18 10:43   ` [PATCH v2 0/2] Testpmd flow update/destroy fixes Dariusz Sosnowski
     [not found]     ` <PAWP190MB2160717526F6D67E34952D2E8B272@PAWP190MB2160.EURP190.PROD.OUTLOOK.COM>
2024-11-18 10:59       ` Dariusz Sosnowski [this message]
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 18:02     ` [PATCH v2 0/2] Testpmd flow update/destroy fixes Danylo Vodopianov
2024-11-18 18:02       ` [PATCH v2 1/2] app/testpmd: fix flow update Danylo Vodopianov
2024-11-18 18:02       ` [PATCH v2 2/2] app/testpmd: fix aged flow destroy Danylo Vodopianov
2024-11-18 18:03     ` [PATCH v3 0/2] Testpmd flow update/destroy fixes Danylo Vodopianov
2024-11-18 18:03       ` [PATCH v3 1/2] app/testpmd: fix flow update Danylo Vodopianov
2024-11-18 18:25         ` Dariusz Sosnowski
2024-11-18 18:03       ` [PATCH v3 2/2] app/testpmd: fix aged flow destroy Danylo Vodopianov
2024-11-18 18:25         ` Dariusz Sosnowski
2024-11-19 22:34       ` [PATCH v3 0/2] Testpmd flow update/destroy fixes Thomas Monjalon
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=CH3PR12MB846024A7DBBA8999191849D4A4272@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).