DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Kaur, Arshdeep" <arshdeep.kaur@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Chintalapalle, Balaji" <balaji.chintalapalle@intel.com>,
	"Beadle, Michael" <michael.beadle@intel.com>
Subject: Re: [RFT] dumpcap: add file-prefix option
Date: Thu, 20 Oct 2022 08:40:31 -0700	[thread overview]
Message-ID: <20221020084031.64ef3fb7@hermes.local> (raw)
In-Reply-To: <DM6PR11MB373715EC02977B2F90120723F02A9@DM6PR11MB3737.namprd11.prod.outlook.com>

On Thu, 20 Oct 2022 10:43:28 +0000
"Kaur, Arshdeep" <arshdeep.kaur@intel.com> wrote:

> Hi Stephen, a gentle reminder.
> 
> Thanks and regards,
> Arshdeep Kaur
> 
> > -----Original Message-----
> > From: Kaur, Arshdeep
> > Sent: Monday, October 17, 2022 10:38 AM
> > To: Stephen Hemminger <stephen@networkplumber.org>; dev@dpdk.org
> > Cc: Chintalapalle, Balaji <balaji.chintalapalle@intel.com>; Beadle, Michael
> > <michael.beadle@intel.com>
> > Subject: RE: [RFT] dumpcap: add file-prefix option
> > 
> > Hi Stephen,
> > 
> > These changes are looking good as compared to
> > http://patches.dpdk.org/project/dpdk/patch/20220912190330.73159-1-
> > stephen@networkplumber.org/.
> > I have tested the changes. Works for me.
> > I am looking for this change in this release. Can you send the v1?
> > 
> > Thanks and regards,
> > Arshdeep Kaur
> >   
> > > -----Original Message-----
> > > From: Stephen Hemminger <stephen@networkplumber.org>
> > > Sent: Tuesday, September 13, 2022 12:34 AM
> > > To: dev@dpdk.org
> > > Cc: Stephen Hemminger <stephen@networkplumber.org>; Kaur,  
> > Arshdeep  
> > > <arshdeep.kaur@intel.com>
> > > Subject: [RFT] dumpcap: add file-prefix option
> > >
> > > When using dumpcap in container environment or with multiple DPDK
> > > processes, it is useful to be able to specify file prefix.
> > >
> > > This version only accepts the long format option used by other  
> > commands.  
> > > If no prefix is specified then the default is used.
> > >
> > > Suggested-by: Arshdeep Kaur <arshdeep.kaur@intel.com>
> > > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> > > ---

Yes, these should be ready to merge.
This is busy time in release cycle for David and Thomas.

  reply	other threads:[~2022-10-20 15:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220829074821.283063-1-arshdeep.kaur@intel.com>
2022-09-06 16:31 ` [PATCH] SCSY-192443 Fix DPDK-dumpcap for XRAN Library Pattan, Reshma
     [not found] ` <20220907162659.260812-1-arshdeep.kaur@intel.com>
2022-09-12  8:54   ` [PATCH v2] dumpcap: add the mutiprocess fileprefix support Kaur, Arshdeep
2022-09-12 12:43 ` Arshdeep Kaur
2022-09-12 14:50   ` Stephen Hemminger
2022-09-12 19:03   ` [RFT] dumpcap: add file-prefix option Stephen Hemminger
2022-09-16  8:19     ` Kaur, Arshdeep
2022-09-16 12:51       ` Ben Magistro
2022-09-16 15:35         ` Stephen Hemminger
2022-09-19 11:19           ` Kaur, Arshdeep
2022-09-23 11:46       ` Kaur, Arshdeep
2022-10-17  5:08     ` Kaur, Arshdeep
2022-10-20 10:43       ` Kaur, Arshdeep
2022-10-20 15:40         ` Stephen Hemminger [this message]
2022-10-20 11:55     ` Kaur, Arshdeep
2022-10-21 13:07       ` David Marchand

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=20221020084031.64ef3fb7@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=arshdeep.kaur@intel.com \
    --cc=balaji.chintalapalle@intel.com \
    --cc=dev@dpdk.org \
    --cc=michael.beadle@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).