DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/scheduler: add mode set get API
Date: Wed, 5 Apr 2017 18:41:59 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D89747804310@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D897478042F4@IRSMSX108.ger.corp.intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of De Lara Guarch,
> Pablo
> Sent: Wednesday, April 05, 2017 7:26 PM
> To: Zhang, Roy Fan; dev@dpdk.org
> Cc: Doherty, Declan
> Subject: Re: [dpdk-dev] [PATCH] crypto/scheduler: add mode set get API
> 
> 
> 
> > -----Original Message-----
> > From: Zhang, Roy Fan
> > Sent: Wednesday, April 05, 2017 5:03 PM
> > To: dev@dpdk.org
> > Cc: De Lara Guarch, Pablo; Doherty, Declan
> > Subject: [PATCH] crypto/scheduler: add mode set get API
> >
> > This patch adds two APIs, "rte_cryptodev_scheduler_mode_set" and
> > "rte_cryptodev_scheduler_mode_get", to crypto scheduler PMD. These
> > two API provides same functionalities as
> > "rte_crpytodev_scheduler_mode_get"
> > and "rte_crpytodev_scheduler_mode_set" and they are proposed to
> > deprecated
> > in 17.08.
> >
> > Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> 
> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>

Applied to dpdk-next-crypto with the following commit message change:

    crypto/scheduler: deprecate get/set mode functions

    This patch deprecates the following functions in 17.05,
    which will be removed in 17.08.
    - rte_crpytodev_scheduler_mode_get()
    - rte_crpytodev_scheduler_mode_set()

    These two new functions replace them, fixing the typo in their names.
    - rte_cryptodev_scheduler_mode_get()
    - rte_cryptodev_scheduler_mode_set()

Thanks,
Pablo

      reply	other threads:[~2017-04-05 18:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 16:03 Fan Zhang
2017-04-05 18:25 ` De Lara Guarch, Pablo
2017-04-05 18:41   ` De Lara Guarch, Pablo [this message]

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=E115CCD9D858EF4F90C690B0DCB4D89747804310@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=roy.fan.zhang@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 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).