From: Stephen Hemminger <stephen@networkplumber.org>
To: Ben Magistro <koncept1@gmail.com>
Cc: "Kaur, Arshdeep" <arshdeep.kaur@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [RFT] dumpcap: add file-prefix option
Date: Fri, 16 Sep 2022 08:35:08 -0700 [thread overview]
Message-ID: <20220916083508.62e44c3a@hermes.local> (raw)
In-Reply-To: <CAKx8PBjPpo_On-u-_tGD65JW5Kztj01JbC15OKsKMPBFqXNKnA@mail.gmail.com>
On Fri, 16 Sep 2022 08:51:59 -0400
Ben Magistro <koncept1@gmail.com> wrote:
> Kaur,
>
> I believe parse_opts() should be called before dpdk_init() now see
> https://patches.dpdk.org/project/dpdk/patch/20220125032545.7704-1-koncept1@gmail.com/
Correct, in main branch parse_opts is before dpdk_init
next prev parent reply other threads:[~2022-09-16 15:35 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 [this message]
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
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=20220916083508.62e44c3a@hermes.local \
--to=stephen@networkplumber.org \
--cc=arshdeep.kaur@intel.com \
--cc=dev@dpdk.org \
--cc=koncept1@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.