From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
Cc: hemant.agrawal@nxp.com, akhil.goyal@nxp.com, dev@dpdk.org,
narender.vangati@intel.com, nikhil.rao@intel.com,
gage.eads@intel.com
Subject: Re: [v4, 2/5] eventdev: add APIs and PMD callbacks for crypto adapter
Date: Wed, 9 May 2018 08:05:23 +0530 [thread overview]
Message-ID: <20180509023521.GB19502@jerin> (raw)
In-Reply-To: <1525808764-109595-3-git-send-email-abhinandan.gujjar@intel.com>
-----Original Message-----
> Date: Wed, 9 May 2018 01:16:01 +0530
> From: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
> To: jerin.jacob@caviumnetworks.com, hemant.agrawal@nxp.com,
> akhil.goyal@nxp.com, dev@dpdk.org
> CC: narender.vangati@intel.com, abhinandan.gujjar@intel.com,
> nikhil.rao@intel.com, gage.eads@intel.com
> Subject: [v4,2/5] eventdev: add APIs and PMD callbacks for crypto adapter
> X-Mailer: git-send-email 1.9.1
>
> Signed-off-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
Please add the git commit log.
next prev parent reply other threads:[~2018-05-09 2:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 19:45 [v4,0/5] eventdev: cover letter - crypto adapter Abhinandan Gujjar
2018-05-08 19:46 ` [v4,1/5] eventdev: introduce event " Abhinandan Gujjar
2018-05-09 2:34 ` Jerin Jacob
2018-05-09 7:01 ` Akhil Goyal
2018-05-09 7:26 ` Gujjar, Abhinandan S
2018-05-08 19:46 ` [v4, 2/5] eventdev: add APIs and PMD callbacks for " Abhinandan Gujjar
2018-05-09 2:35 ` Jerin Jacob [this message]
2018-05-08 19:46 ` [v4,3/5] eventdev: add crypto adapter implementation Abhinandan Gujjar
2018-05-09 2:36 ` [v4, 3/5] " Jerin Jacob
2018-05-08 19:46 ` [v4,4/5] test: add event crypto adapter auto-test Abhinandan Gujjar
2018-05-08 19:46 ` [v4,5/5] doc: add event crypto adapter documentation Abhinandan Gujjar
2018-05-09 2:45 ` [v4, 5/5] " Jerin Jacob
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=20180509023521.GB19502@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=abhinandan.gujjar@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=gage.eads@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=narender.vangati@intel.com \
--cc=nikhil.rao@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.