From: "Mokhtar, Amr" <amr.mokhtar@intel.com>
To: David Marchand <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"nhorman@tuxdriver.com" <nhorman@tuxdriver.com>,
"tredaelli@redhat.com" <tredaelli@redhat.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-stable] [PATCH] bbdev: add missing experimental tags
Date: Wed, 5 Dec 2018 16:46:59 +0000 [thread overview]
Message-ID: <3D3765A8CDB52A4C8B410430AA19CB23709052A5@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <1543957065-20990-1-git-send-email-david.marchand@redhat.com>
> -----Original Message-----
> From: David Marchand [mailto:david.marchand@redhat.com]
> Sent: Tuesday 4 December 2018 20:58
> To: dev@dpdk.org
> Cc: stable@dpdk.org; nhorman@tuxdriver.com; tredaelli@redhat.com;
> Yigit, Ferruh <ferruh.yigit@intel.com>; Mokhtar, Amr
> <amr.mokhtar@intel.com>
> Subject: [PATCH] bbdev: add missing experimental tags
>
> Those two symbols are missing the experimental tag in the library
> header.
> Because of this, a user can try to call this symbol without being aware
> this is an experimental api (neither compilation nor link warning).
>
> Fixes: 4935e1e9f76e ("bbdev: introduce wireless base band device lib")
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
Acked-by: Amr Mokhtar <amr.mokhtar@intel.com>
next prev parent reply other threads:[~2018-12-05 16:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 20:57 David Marchand
2018-12-05 12:23 ` Neil Horman
2018-12-05 16:46 ` Mokhtar, Amr [this message]
2018-12-14 9:54 ` [dpdk-stable] [dpdk-dev] " Akhil Goyal
2018-12-14 10:00 ` David Marchand
2018-12-14 12:35 ` Neil Horman
2018-12-14 12:52 ` Mokhtar, Amr
2018-12-18 10:37 ` David Marchand
2018-12-18 10:43 ` Akhil Goyal
2018-12-18 10:48 ` David Marchand
2018-12-19 9:20 ` Mokhtar, Amr
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=3D3765A8CDB52A4C8B410430AA19CB23709052A5@IRSMSX104.ger.corp.intel.com \
--to=amr.mokhtar@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).