From: Olivier Matz <olivier.matz@6wind.com>
To: dev@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: santosh.shukla@caviumnetworks.com,
John McNamara <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] eal: remove deprecated function returning mbuf pool ops name
Date: Tue, 26 Jun 2018 11:51:38 +0200 [thread overview]
Message-ID: <20180626095138.pmxeycgk2ebwrhjt@platinum> (raw)
In-Reply-To: <20180626091236.30429-1-olivier.matz@6wind.com>
On Tue, Jun 26, 2018 at 11:12:35AM +0200, Olivier Matz wrote:
> rte_eal_mbuf_default_mempool_ops() is replaced by
> rte_mbuf_best_mempool_ops().
>
> Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
Self nack, rebase issue between these 2 patches.
Thanks Thomas for spotting it.
Will send a v2.
next prev parent reply other threads:[~2018-06-26 9:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 9:12 Olivier Matz
2018-06-26 9:12 ` [dpdk-dev] [PATCH 2/2] eal: remove experimental tag from user mbuf pool ops func Olivier Matz
2018-06-26 9:51 ` Olivier Matz [this message]
2018-06-26 9:56 ` [dpdk-dev] [PATCH v2 1/2] eal: remove deprecated function returning mbuf pool ops name Olivier Matz
2018-06-26 9:56 ` [dpdk-dev] [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 ` [dpdk-dev] [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 ` [dpdk-dev] [PATCH v3 " Olivier Matz
2018-08-07 21:34 ` [dpdk-dev] [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 ` [dpdk-dev] [PATCH v3 1/2] eal: remove deprecated function returning mbuf pool ops name Hemant
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=20180626095138.pmxeycgk2ebwrhjt@platinum \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=john.mcnamara@intel.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).