From: Akhil Goyal <gakhil@marvell.com>
To: Akhil Goyal <gakhil@marvell.com>,
Nicolas Chautru <nicolas.chautru@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"nipun.gupta@nxp.com" <nipun.gupta@nxp.com>
Cc: "trix@redhat.com" <trix@redhat.com>,
"mingshan.zhang@intel.com" <mingshan.zhang@intel.com>,
"arun.joshi@intel.com" <arun.joshi@intel.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"mdr@ashroe.eu" <mdr@ashroe.eu>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH v1] bbdev: remove experimental tag from API
Date: Sun, 31 Oct 2021 19:17:08 +0000 [thread overview]
Message-ID: <CO6PR18MB44847D16F8E8F8A99BAEC720D8899@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB448484055B25681BD9560A6CD8B29@CO6PR18MB4484.namprd18.prod.outlook.com>
>
> > This promotes the bbdev interface to stable.
> > Overdue for some time as bbdev interface has been stable.
> >
> > Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> > ---
> Acked-by: Akhil Goyal <gakhil@marvell.com>
>
> If anybody has any objections please raise or else this patch
> Will be merged in RC1.
No response received.
Applied to dpdk-next-crypto
next prev parent reply other threads:[~2021-10-31 19:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 16:25 [dpdk-dev] " Nicolas Chautru
2021-08-31 16:25 ` Nicolas Chautru
2021-10-08 19:29 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-10-31 19:17 ` Akhil Goyal [this message]
2021-11-06 8:58 ` Thomas Monjalon
2021-08-31 16:38 ` [dpdk-dev] " David Marchand
2021-09-01 3:52 ` Hemant Agrawal
2021-09-01 11:14 ` Kinsella, Ray
2021-09-01 14:54 ` Chautru, Nicolas
2021-09-13 19:44 ` Maxime Coquelin
2021-09-14 3:13 ` Hemant Agrawal
2021-09-01 14:51 ` Chautru, Nicolas
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=CO6PR18MB44847D16F8E8F8A99BAEC720D8899@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=arun.joshi@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=mdr@ashroe.eu \
--cc=mingshan.zhang@intel.com \
--cc=nicolas.chautru@intel.com \
--cc=nipun.gupta@nxp.com \
--cc=thomas@monjalon.net \
--cc=trix@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).