From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: nikhil.rao@intel.com, harry.van.haaren@intel.com,
anoob.joseph@caviumnetworks.com, dev@dpdk.org
Subject: Re: [PATCH] examples/eventdev_pipeline: add Tx adapter support
Date: Mon, 17 Sep 2018 19:47:58 +0530 [thread overview]
Message-ID: <20180917141756.GA22435@jerin> (raw)
In-Reply-To: <20180905134554.25243-1-pbhagavatula@caviumnetworks.com>
-----Original Message-----
> Date: Wed, 5 Sep 2018 19:15:54 +0530
> From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> To: jerin.jacob@caviumnetworks.com, nikhil.rao@intel.com,
> harry.van.haaren@intel.com, anoob.joseph@caviumnetworks.com
> Cc: dev@dpdk.org, Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> Subject: [dpdk-dev] [PATCH] examples/eventdev_pipeline: add Tx adapter
> support
> X-Mailer: git-send-email 2.18.0
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> ---
> This patch depends on the following series:
> http://patches.dpdk.org/project/dpdk/list/?series=1121
>
> examples/eventdev_pipeline/main.c | 62 ++--
> examples/eventdev_pipeline/pipeline_common.h | 31 +-
> .../pipeline_worker_generic.c | 273 +++++-------------
> .../eventdev_pipeline/pipeline_worker_tx.c | 130 +++++----
> 4 files changed, 186 insertions(+), 310 deletions(-)
Harry and Nikhil,
As examples/eventdev_pipeline and Tx adapter maintainers, Please
review this examples/eventdev_pipeline changes.
next prev parent reply other threads:[~2018-09-17 14:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 13:45 [PATCH] examples/eventdev_pipeline: add Tx adapter support Pavan Nikhilesh
2018-09-17 14:17 ` Jerin Jacob [this message]
2018-09-19 2:54 ` Rao, Nikhil
2018-09-19 10:42 ` Pavan Nikhilesh
2018-09-20 2:18 ` Rao, Nikhil
2018-09-21 7:44 ` Rao, Nikhil
2018-09-24 9:51 ` Pavan Nikhilesh
2018-09-24 10:12 ` [PATCH v2] " Pavan Nikhilesh
2018-09-26 12:56 ` Rao, Nikhil
2018-09-28 11:15 ` Jerin Jacob
2018-10-03 8:47 ` Rao, Nikhil
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=20180917141756.GA22435@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=anoob.joseph@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=nikhil.rao@intel.com \
--cc=pbhagavatula@caviumnetworks.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.