patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Amr Mokhtar <amr.mokhtar@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"tredaelli@redhat.com" <tredaelli@redhat.com>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>,
	"nhorman@tuxdriver.com" <nhorman@tuxdriver.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] bbdev: add missing APIs to map file
Date: Tue, 18 Dec 2018 06:46:38 +0000	[thread overview]
Message-ID: <bfa89b12-8896-71a6-a3a6-b60fcb7a71ea@nxp.com> (raw)
In-Reply-To: <1544804523-66689-1-git-send-email-amr.mokhtar@intel.com>



On 12/14/2018 9:52 PM, Amr Mokhtar wrote:
> some application facing functions are missing from
> the map file. these are added by this patch.
>
> Signed-off-by: Amr Mokhtar <amr.mokhtar@intel.com>
> ---
>   lib/librte_bbdev/rte_bbdev_version.map | 4 ++++
>   1 file changed, 4 insertions(+)
>
> diff --git a/lib/librte_bbdev/rte_bbdev_version.map b/lib/librte_bbdev/rte_bbdev_version.map
> index d3b81ea..c392f41 100644
> --- a/lib/librte_bbdev/rte_bbdev_version.map
> +++ b/lib/librte_bbdev/rte_bbdev_version.map
> @@ -6,9 +6,13 @@ EXPERIMENTAL {
>   	rte_bbdev_callback_unregister;
>   	rte_bbdev_close;
>   	rte_bbdev_count;
> +	rte_bbdev_dec_op_alloc_bulk;
> +	rte_bbdev_dec_op_free_bulk;
>   	rte_bbdev_dequeue_dec_ops;
>   	rte_bbdev_dequeue_enc_ops;
>   	rte_bbdev_devices;
> +	rte_bbdev_enc_op_alloc_bulk;
> +	rte_bbdev_enc_op_free_bulk
semicolon is also missing.
>   	rte_bbdev_enqueue_dec_ops;
>   	rte_bbdev_enqueue_enc_ops;
>   	rte_bbdev_find_next;


      parent reply	other threads:[~2018-12-18  6:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14 16:22 [dpdk-stable] " Amr Mokhtar
2018-12-17  9:55 ` [dpdk-stable] [dpdk-dev] " Akhil Goyal
2018-12-18  6:46 ` Akhil Goyal [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=bfa89b12-8896-71a6-a3a6-b60fcb7a71ea@nxp.com \
    --to=akhil.goyal@nxp.com \
    --cc=amr.mokhtar@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=nhorman@tuxdriver.com \
    --cc=stable@dpdk.org \
    --cc=tredaelli@redhat.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).