From: Olivier Matz <olivier.matz@6wind.com>
To: santosh <santosh.shukla@caviumnetworks.com>
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mbuf: remove experimental tag from pool ops functions
Date: Mon, 25 Jun 2018 17:27:29 +0200 [thread overview]
Message-ID: <20180625152729.2zx2fg2c35fxurbd@platinum> (raw)
In-Reply-To: <0661870c-631f-e89e-87d8-d9b6aeb33992@caviumnetworks.com>
On Mon, Jun 11, 2018 at 07:49:37PM +0530, santosh wrote:
>
> On Monday 11 June 2018 07:37 PM, Jerin Jacob wrote:
> > -----Original Message-----
> >> Date: Tue, 5 Jun 2018 11:54:11 +0530
> >> From: Hemant Agrawal <hemant.agrawal@nxp.com>
> >> To: dev@dpdk.org
> >> CC: olivier.matz@6wind.com, santosh.shukla@caviumnetworks.com, Hemant
> >> Agrawal <hemant.agrawal@nxp.com>
> >> Subject: [dpdk-dev] [PATCH] mbuf: remove experimental tag from pool ops
> >> functions
> >> X-Mailer: git-send-email 2.7.4
> >>
> >> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
>
> Acked-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>
Shouldn't we add something in doc/guides/rel_notes/release_18_08.rst,
like it's done for instance in 60df5711972e ("service: remove experimental
tags")?
Apart from this,
Acked-by: Olivier Matz <olivier.matz@6wind.com>
By the way I'm preparing a patch to remove rte_eal_mbuf_default_mempool_ops()
which is deprecated and remove experimental tag from
rte_eal_mbuf_user_pool_ops().
next prev parent reply other threads:[~2018-06-25 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 6:24 Hemant Agrawal
2018-06-08 9:17 ` Andrew Rybchenko
2018-06-11 14:07 ` Jerin Jacob
2018-06-11 14:19 ` santosh
2018-06-25 15:27 ` Olivier Matz [this message]
2018-07-26 21:39 ` Thomas Monjalon
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=20180625152729.2zx2fg2c35fxurbd@platinum \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=santosh.shukla@caviumnetworks.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).