From: "Etelson, Gregory" <getelson@nvidia.com>
To: "Singh, Aman Deep" <aman.deep.singh@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"yuying.zhang@intel.com" <yuying.zhang@intel.com>,
Dariusz Sosnowski <dsosnowski@nvidia.com>
Subject: RE: [PATCH v4 1/1] testpmd: add hairpin-map parameter
Date: Sun, 22 Sep 2024 12:33:20 +0300 (IDT) [thread overview]
Message-ID: <b39ebfb2-8d3a-c4ff-e6e-e3aff183735@nvidia.com> (raw)
In-Reply-To: <IA1PR11MB6074AEC8165D83762A9DA10BA36C2@IA1PR11MB6074.namprd11.prod.outlook.com>
On Fri, 20 Sep 2024, Singh, Aman Deep wrote:
> External email: Use caution opening links or attachments
>
>
> Hi Gregory,
> Can you please resolve the compilation issues seen with this patch.
>
Hello,
I've posted v5.
Regards,
Gregory
prev parent reply other threads:[~2024-09-22 9:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 10:10 [PATCH] testpmd: add hairpin-map parameter Gregory Etelson
2023-09-20 12:22 ` [PATCH v2] " Gregory Etelson
2023-09-28 15:36 ` [PATCH v3] " Gregory Etelson
2023-12-14 8:06 ` Dariusz Sosnowski
2024-03-01 18:54 ` Ferruh Yigit
2024-03-05 3:04 ` Gregory Etelson
2024-09-22 6:50 ` [PATCH v5 1/1] " Gregory Etelson
2024-10-16 8:11 ` Ferruh Yigit
2024-10-28 10:23 ` Gregory Etelson
2024-10-29 21:51 ` Ferruh Yigit
2024-10-29 22:23 ` Stephen Hemminger
2024-10-30 7:37 ` [PATCH v6] testpmd: add hairpin map parameter Gregory Etelson
2024-10-30 19:37 ` Stephen Hemminger
2024-10-31 5:02 ` Etelson, Gregory
2024-10-31 4:58 ` [PATCH v7] " Gregory Etelson
2024-10-31 15:51 ` Stephen Hemminger
2024-11-01 2:52 ` Ferruh Yigit
2024-09-11 5:08 ` [PATCH v4 1/1] testpmd: add hairpin-map parameter Gregory Etelson
2024-09-20 13:48 ` Singh, Aman Deep
2024-09-22 9:33 ` Etelson, Gregory [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=b39ebfb2-8d3a-c4ff-e6e-e3aff183735@nvidia.com \
--to=getelson@nvidia.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--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 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.