DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>,
	<thomas@monjalon.net>, <jerin.jacob@caviumnetworks.com>,
	<hemant.agrawal@nxp.com>, <fiona.trahe@intel.com>,
	<deepak.k.jain@intel.com>, <john.griffin@intel.com>,
	 <declan.doherty@intel.com>, <john.mcnamara@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: announce crypto vdev init removal
Date: Thu, 3 Aug 2017 16:12:31 +0530	[thread overview]
Message-ID: <2fb9eab9-e04b-6a81-8871-52b64385b9f0@nxp.com> (raw)
In-Reply-To: <20170803021221.38955-1-pablo.de.lara.guarch@intel.com>

On 8/3/2017 7:42 AM, Pablo de Lara wrote:
> In order to remove all dependencies on vdev for cryptodev,
> the implementation of rte_cryptodev_vdev_pmd_init() function
> needs to be moved to rte_cryptodev_vdev.h, and all crypto
> vdevs will include it, and therefore, this function will
> be removed as a public API.
> 
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
>   doc/guides/rel_notes/deprecation.rst | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index f6bd910..63ffad1 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -69,3 +69,8 @@ Deprecation Notices
>     be removed in 17.11:
>   
>     - ``rte_cryptodev_create_vdev``
> +
> +* cryptodev: the following function will be static in 17.11 and included
> +  by all crypto drivers, therefore, will not be public:
> +
> +  - ``rte_cryptodev_vdev_pmd_init``
> 

Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

  parent reply	other threads:[~2017-08-03 10:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03  2:12 Pablo de Lara
2017-08-03 10:38 ` Mcnamara, John
2017-08-03 10:42 ` Akhil Goyal [this message]
2017-08-08 10:12   ` Thomas Monjalon
2017-08-03 14:02 ` Jain, Deepak K
2017-08-03 14:13 ` Jain, Deepak K

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=2fb9eab9-e04b-6a81-8871-52b64385b9f0@nxp.com \
    --to=akhil.goyal@nxp.com \
    --cc=declan.doherty@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=john.griffin@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=pablo.de.lara.guarch@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).