From: Sunil Kumar Kori <skori@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Rakesh Kudurumalla <rkudurumalla@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: RE: [EXTERNAL] Re: [PATCH v2 1/1] app/graph: generate cmdline boilerplate
Date: Thu, 7 Mar 2024 07:06:03 +0000 [thread overview]
Message-ID: <CO6PR18MB38607A193EF401F1E0ED6A7EB4202@CO6PR18MB3860.namprd18.prod.outlook.com> (raw)
In-Reply-To: <7636191.nlapOpYt14@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Thursday, March 7, 2024 3:22 AM
> To: Sunil Kumar Kori <skori@marvell.com>
> Cc: Rakesh Kudurumalla <rkudurumalla@marvell.com>; dev@dpdk.org;
> Bruce Richardson <bruce.richardson@intel.com>
> Subject: [EXTERNAL] Re: [PATCH v2 1/1] app/graph: generate cmdline
> boilerplate
>
> Prioritize security for external emails: Confirm sender and content safety
> before clicking links or opening attachments
>
> ----------------------------------------------------------------------
> 12/12/2023 18:05, skori@marvell.com:
> > From: Sunil Kumar Kori <skori@marvell.com>
> >
> > Use the dpdk-cmdline-gen script to autogenerate all the boilerplate
> > structs and defines for the commandline part of the application.
> >
> > Signed-off-by: Sunil Kumar Kori <skori@marvell.com>
> > Acked-by: Bruce Richardson <bruce.richardson@intel.com>
>
> Sorry this patch was not applied on time, and it requires a bit of rebasing
> work.
> Please could you provide a v3?
>
Sure. I will rework and send v3 asap.
next prev parent reply other threads:[~2024-03-07 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 7:12 [PATCH] " skori
2023-12-07 10:29 ` Bruce Richardson
2023-12-12 17:05 ` [PATCH v2 1/1] " skori
2023-12-18 8:48 ` Nithin Dabilpuram
2024-03-06 21:52 ` Thomas Monjalon
2024-03-07 7:06 ` Sunil Kumar Kori [this message]
2024-03-07 9:41 ` [EXTERNAL] " Sunil Kumar Kori
2024-03-07 9:40 ` [PATCH v3 " skori
2024-03-07 15:31 ` Thomas Monjalon
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=CO6PR18MB38607A193EF401F1E0ED6A7EB4202@CO6PR18MB3860.namprd18.prod.outlook.com \
--to=skori@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=rkudurumalla@marvell.com \
--cc=thomas@monjalon.net \
/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).