From: David Marchand <david.marchand@redhat.com>
To: "Kaur, Arshdeep" <arshdeep.kaur@intel.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [RFT] dumpcap: add file-prefix option
Date: Fri, 21 Oct 2022 15:07:42 +0200 [thread overview]
Message-ID: <CAJFAV8wgzY75w92y-VWLM+d6MMmwgFEaTxQzzAmVs4hLXT9WWg@mail.gmail.com> (raw)
In-Reply-To: <DM6PR11MB37376EE0626860B13E90191FF02A9@DM6PR11MB3737.namprd11.prod.outlook.com>
On Thu, Oct 20, 2022 at 1:55 PM Kaur, Arshdeep <arshdeep.kaur@intel.com> wrote:
> >
> > 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>
> Acked-by: Arshdeep Kaur <arshdeep.kaur@intel.com>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2022-10-21 13:07 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
2022-10-20 11:55 ` Kaur, Arshdeep
2022-10-21 13:07 ` David Marchand [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=CAJFAV8wgzY75w92y-VWLM+d6MMmwgFEaTxQzzAmVs4hLXT9WWg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=arshdeep.kaur@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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).