From: Hemant <hemant.agrawal@nxp.com>
To: Olivier Matz <olivier.matz@6wind.com>,
dev@dpdk.org, John McNamara <john.mcnamara@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Santosh Shukla <santosh.shukla@caviumnetworks.com>
Subject: Re: [PATCH v3 1/2] eal: remove deprecated function returning mbuf pool ops name
Date: Wed, 8 Aug 2018 17:10:02 +0530 [thread overview]
Message-ID: <4db00a0b-2b2d-b733-8cd5-aa98a3da5920@nxp.com> (raw)
In-Reply-To: <20180807213443.24847-1-zer0@droids-corp.org>
On 8/8/2018 3:04 AM, Olivier Matz wrote:
> From: Olivier Matz <olivier.matz@6wind.com>
>
> rte_eal_mbuf_default_mempool_ops() is replaced by
> rte_mbuf_best_mempool_ops().
>
> Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
> Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com>
> Acked-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>
> ---
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
prev parent reply other threads:[~2018-08-08 11:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 9:12 [PATCH 1/2] eal: remove deprecated function returning mbuf pool ops name Olivier Matz
2018-06-26 9:12 ` [PATCH 2/2] eal: remove experimental tag from user mbuf pool ops func Olivier Matz
2018-06-26 9:51 ` [PATCH 1/2] eal: remove deprecated function returning mbuf pool ops name Olivier Matz
2018-06-26 9:56 ` [PATCH v2 " Olivier Matz
2018-06-26 9:56 ` [PATCH v2 2/2] eal: remove experimental tag from user mbuf pool ops func Olivier Matz
2018-06-27 15:06 ` santosh
2018-06-26 12:16 ` [PATCH v2 1/2] eal: remove deprecated function returning mbuf pool ops name Burakov, Anatoly
2018-06-27 15:08 ` santosh
2018-07-26 21:42 ` Thomas Monjalon
2018-08-05 21:45 ` Thomas Monjalon
2018-08-07 21:34 ` [PATCH v3 " Olivier Matz
2018-08-07 21:34 ` [PATCH v3 2/2] eal: remove experimental tag from user mbuf pool ops func Olivier Matz
2018-08-08 11:40 ` Hemant
2018-08-08 22:46 ` Thomas Monjalon
2018-08-08 11:40 ` Hemant [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=4db00a0b-2b2d-b733-8cd5-aa98a3da5920@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=olivier.matz@6wind.com \
--cc=santosh.shukla@caviumnetworks.com \
--cc=thomas@monjalon.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.