From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Shah, Rahul R" <rahul.r.shah@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v3] port: Eventdev port support added in the rte_port library
Date: Fri, 25 Oct 2019 15:39:28 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891268E94E199@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20191001180526.3259-1-rahul.r.shah@intel.com>
Hi Rahul,
Thank you for your work!
> -----Original Message-----
> From: Shah, Rahul R
> Sent: Tuesday, October 1, 2019 7:05 PM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Cc: dev@dpdk.org
> Subject: [PATCH v3] port: Eventdev port support added in the rte_port
> library
>
> Adding a new port type called eventdev to the
> rte_port library.
>
> Signed-off-by: Rahul Shah <rahul.r.shah@intel.com>
> ---
> lib/librte_port/Makefile | 4 +-
> lib/librte_port/meson.build | 8 +-
> lib/librte_port/rte_port_eventdev.c | 585
> +++++++++++++++++++++++++++
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
The only cosmetic change I would suggest is for the name of the patch, which can be made shorter:
Port: add eventdev port type
Regards,
Cristian
next prev parent reply other threads:[~2019-10-25 15:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 18:05 Rahul Shah
2019-10-25 15:35 ` Thomas Monjalon
2019-10-25 15:40 ` Dumitrescu, Cristian
2019-10-25 15:39 ` Dumitrescu, Cristian [this message]
2019-10-25 16:29 ` Thomas Monjalon
2019-10-31 17:03 ` Ferruh Yigit
2019-11-04 11:24 ` Bruce Richardson
2019-11-04 12:03 ` Shah, Rahul R
2019-11-04 11:24 ` Shah, Rahul R
2019-11-05 15:59 ` Ferruh Yigit
2019-11-05 16:13 ` Shah, Rahul R
2019-11-05 16:22 ` Ferruh Yigit
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=3EB4FA525960D640B5BDFFD6A3D891268E94E199@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=rahul.r.shah@intel.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).