From: Thomas Monjalon <thomas@monjalon.net>
To: Amr Mokhtar <amr.mokhtar@intel.com>
Cc: stable@dpdk.org, dev@dpdk.org, tredaelli@redhat.com,
akhil.goyal@nxp.com, david.marchand@redhat.com,
nhorman@tuxdriver.com
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v2] bbdev: add missing APIs to map file and tag all experimental
Date: Wed, 19 Dec 2018 19:28:07 +0100 [thread overview]
Message-ID: <6466374.ddQSjb7VuA@xps> (raw)
In-Reply-To: <1545213627-128738-1-git-send-email-amr.mokhtar@intel.com>
19/12/2018 11:00, Amr Mokhtar:
> - add missing APIs to map file
> - add experimental tag to all bbdev APIs
>
> Signed-off-by: Amr Mokhtar <amr.mokhtar@intel.com>
Applied, thanks
Please do not forget --in-reply-to when sending a v2.
prev parent reply other threads:[~2018-12-19 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 10:00 [dpdk-dev] " Amr Mokhtar
2018-12-19 18:28 ` Thomas Monjalon [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=6466374.ddQSjb7VuA@xps \
--to=thomas@monjalon.net \
--cc=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).