From: Thomas Monjalon <thomas@monjalon.net>
To: cristian.dumitrescu@intel.com, Yogesh Jangra <yogesh.jangra@intel.com>
Cc: dev@dpdk.org, venkata.suresh.kumar.p@intel.com,
churchill.khangar@intel.com
Subject: Re: [dpdk-dev] [PATCH] port: configure loop count for source port
Date: Mon, 25 Oct 2021 14:31:07 +0200 [thread overview]
Message-ID: <10158385.XEpRWt7DYZ@thomas> (raw)
In-Reply-To: <1631874725-213201-1-git-send-email-yogesh.jangra@intel.com>
17/09/2021 12:32, Yogesh Jangra:
> Add support for configurable number of loops through the input PCAP
> file for the source port. Added an additional parameter to source
> port CLI command.
>
> Signed-off-by: Yogesh Jangra <yogesh.jangra@intel.com>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Applied, thanks.
prev parent reply other threads:[~2021-10-25 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 10:32 Yogesh Jangra
2021-10-25 12:31 ` Thomas Monjalon [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=10158385.XEpRWt7DYZ@thomas \
--to=thomas@monjalon.net \
--cc=churchill.khangar@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=venkata.suresh.kumar.p@intel.com \
--cc=yogesh.jangra@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).