From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Cian Ferriter <cian.ferriter@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 19.08 v3 1/2] net/pcap: use a struct to pass user options
Date: Fri, 28 Jun 2019 16:30:03 +0100 [thread overview]
Message-ID: <0b3ed9f3-1ef8-5f68-dbe8-f7132fba9ac5@intel.com> (raw)
In-Reply-To: <20190614144337.17177-1-cian.ferriter@intel.com>
On 6/14/2019 3:43 PM, Cian Ferriter wrote:
> The argument lists on some of the device creation functions are quite
> large. Using a struct to hold the user options parsed in
> 'pmd_pcap_probe' will allow for cleaner function calls and definitions.
> Adding user options will also be easier.
>
> Signed-off-by: Cian Ferriter <cian.ferriter@intel.com>
For series,
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Series applied to dpdk-next-net/master, thanks.
(Mentioned changes done while merging)
prev parent reply other threads:[~2019-06-28 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 14:43 Cian Ferriter
2019-06-14 14:43 ` [dpdk-dev] [PATCH 19.08 v3 2/2] net/pcap: enable infinitely rxing a pcap file Cian Ferriter
2019-06-27 17:56 ` Ferruh Yigit
2019-06-28 12:32 ` Ferriter, Cian
2019-06-28 13:00 ` Ferruh Yigit
2019-06-28 15:30 ` Ferruh Yigit [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=0b3ed9f3-1ef8-5f68-dbe8-f7132fba9ac5@intel.com \
--to=ferruh.yigit@intel.com \
--cc=cian.ferriter@intel.com \
--cc=dev@dpdk.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).