From: "Wiles, Keith" <keith.wiles@intel.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH] mbuf: pktmbuf pool create helper for specific mempool ops
Date: Tue, 16 Jan 2018 14:59:02 +0000 [thread overview]
Message-ID: <29B6B50F-B9F2-4919-892B-32C185821474@intel.com> (raw)
In-Reply-To: <20180116145207.as6nuws4hamhvhs4@platinum>
> On Jan 16, 2018, at 8:52 AM, Olivier Matz <olivier.matz@6wind.com> wrote:
>
> On Fri, Dec 22, 2017 at 05:00:11PM +0530, Hemant Agrawal wrote:
>> Introduce a new helper for pktmbuf pool, which will allow
>> the application to optionally specify the mempool ops name
>> as well.
>>
>> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
>> ---
>
> Hi Hemant,
>
> It looks this patch is now in another patchset:
> http://dpdk.org/dev/patchwork/patch/33719/
>
> Can it be marked as superseeded in patchwork?
I can mark my patch.
>
> Thanks
Regards,
Keith
next prev parent reply other threads:[~2018-01-16 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 11:30 Hemant Agrawal
2017-12-22 13:53 ` Wiles, Keith
2018-01-16 14:52 ` Olivier Matz
2018-01-16 14:59 ` Wiles, Keith [this message]
2018-01-17 5:29 ` Hemant Agrawal
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=29B6B50F-B9F2-4919-892B-32C185821474@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=olivier.matz@6wind.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).