From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
Cc: declan.doherty@intel.com, dev@dpdk.org
Subject: Re: [PATCH] doc: announce crypto device type enumeration removal
Date: Mon, 8 May 2017 16:35:07 +0530 [thread overview]
Message-ID: <20170508110506.GB16391@jerin> (raw)
In-Reply-To: <20170505112419.14965-1-slawomirx.mrozowicz@intel.com>
-----Original Message-----
> Date: Fri, 5 May 2017 13:24:19 +0200
> From: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
> To: declan.doherty@intel.com
> CC: dev@dpdk.org, Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
> Subject: [dpdk-dev] [PATCH] doc: announce crypto device type enumeration
> removal
> X-Mailer: git-send-email 2.9.3
>
> Refer to RFC patch - cryptodev: remove crypto device type enumeration
>
> It is planned to remove device type enumeration rte_cryptodev_type from
> library to remove the coupling between crypto PMD and the librte_cryptodev.
>
> In this case following stuctures will be changed: rte_cryptodev_session,
> rte_cryptodev_sym_session, rte_cryptodev_info, rte_cryptodev.
>
> It is planned to change the function rte_cryptodev_count_devtype().
> The function prototype doesn’t clearly show the operation.
> From next release 17.08 the dev_type will be changed to driver_id.
> So the function name will change to rte_cryptodev_device_count_by_driver().
>
> Signed-off-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
next prev parent reply other threads:[~2017-05-08 11:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 11:24 [PATCH] doc: announce crypto device type enumeration removal Slawomir Mrozowicz
2017-05-08 9:50 ` De Lara Guarch, Pablo
2017-05-11 0:48 ` Thomas Monjalon
2017-05-08 10:33 ` Declan Doherty
2017-05-08 11:05 ` Jerin Jacob [this message]
2017-05-08 13:30 ` Trahe, Fiona
2017-05-09 8:55 ` Akhil Goyal
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=20170508110506.GB16391@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=slawomirx.mrozowicz@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.