From: Stephen Hemminger <stephen@networkplumber.org>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: <dev@dpdk.org>, Hemant Agrawal <hemant.agrawal@nxp.com>,
<thomas.monjalon@6wind.com>, <declan.doherty@intel.com>,
<pablo.de.lara.guarch@intel.com>, <jblunck@infradead.org>
Subject: Re: [dpdk-dev] [PATCH] cryptodev: decouple from PCI device
Date: Tue, 24 Jan 2017 20:54:18 -0800 [thread overview]
Message-ID: <20170124205418.40ca5795@xeon-e3> (raw)
In-Reply-To: <aa100e68-5fbf-7654-bc1b-8fd425b31a96@nxp.com>
On Wed, 25 Jan 2017 10:18:01 +0530
Shreyansh Jain <shreyansh.jain@nxp.com> wrote:
> On Wednesday 18 January 2017 02:46 PM, Hemant Agrawal wrote:
> > This makes struct rte_cryptodev independent of struct rte_pci_device by
> > replacing it with a pointer to the generic struct rte_device.
> >
> > This is inline with the recent changes in ethdev
> >
> > Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> > ---
> > drivers/crypto/qat/qat_qp.c | 12 +++++++++---
> > drivers/crypto/qat/rte_qat_cryptodev.c | 6 +++---
> > lib/librte_cryptodev/rte_cryptodev.c | 6 +++---
> > lib/librte_cryptodev/rte_cryptodev.h | 4 ++--
> > 4 files changed, 17 insertions(+), 11 deletions(-)
> >
>
> Next step would be to remove rte_pci_driver from eth_driver
> and rte_cryptodev_driver and make it generic.
>
> Reviewed-by: Shreyansh Jain <shreyansh.jain@nxp.com>
>
Agreed.
next prev parent reply other threads:[~2017-01-25 4:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 9:16 Hemant Agrawal
2017-01-24 18:10 ` Griffin, John
2017-01-25 4:48 ` Shreyansh Jain
2017-01-25 4:54 ` Stephen Hemminger [this message]
2017-01-25 9:07 ` De Lara Guarch, Pablo
-- strict thread matches above, loose matches on Subject: below --
2017-01-17 18:52 [dpdk-dev] [PATCHv4 00/33] NXP DPAA2 PMD Hemant Agrawal
2017-01-19 13:23 ` [dpdk-dev] [PATCHv5 " Hemant Agrawal
2017-01-19 13:23 ` [dpdk-dev] [PATCH] cryptodev: decouple from PCI device Hemant Agrawal
2017-01-19 13:27 ` Hemant Agrawal
2017-01-20 12:28 ` De Lara Guarch, Pablo
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=20170124205418.40ca5795@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jblunck@infradead.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=shreyansh.jain@nxp.com \
--cc=thomas.monjalon@6wind.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).