From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
jerin.jacob@caviumnetworks.com,
santosh.shukla@caviumnetworks.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] net/octeontx: register fpa as platform HW mempool
Date: Mon, 5 Feb 2018 16:14:59 +0530 [thread overview]
Message-ID: <20180205104458.65f5guhfvedh2lrn@Pavan-LT> (raw)
In-Reply-To: <e5901329-697e-f750-f50d-c9962500e288@intel.com>
On Mon, Feb 05, 2018 at 10:34:00AM +0000, Ferruh Yigit wrote:
> On 2/4/2018 3:33 PM, Pavan Nikhilesh wrote:
> > Register octeontx-fpavf as platform HW mempool when net/octeontx pmd is
> > used.
> >
> > Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> > ---
> >
> > v2 Changes:
> > - fixed compilation issues caused by using experimental API in both meson and
> > make.
> >
> > drivers/net/octeontx/Makefile | 2 ++
> > drivers/net/octeontx/meson.build | 2 ++
>
> Meson patches are still going through the Bruce's tree. Can you please make this
> two separate patches (not patchset), I can get the driver one and Makefile,
> Bruce can get meson one.
Just a heads up doing so would break meson build on next-net branch.
Will split the patches and resend them.
>
> Thanks,
> ferruh
Thanks,
Pavan.
next prev parent reply other threads:[~2018-02-05 10:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 15:45 [dpdk-dev] [PATCH] " Pavan Nikhilesh
2018-01-31 19:51 ` Ferruh Yigit
2018-02-04 15:33 ` [dpdk-dev] [PATCH v2] " Pavan Nikhilesh
2018-02-05 5:41 ` santosh
2018-02-05 10:34 ` Ferruh Yigit
2018-02-05 10:44 ` Pavan Nikhilesh [this message]
2018-02-05 11:46 ` Bruce Richardson
2018-02-05 18:55 ` Ferruh Yigit
2018-02-05 11:44 ` Bruce Richardson
2018-02-05 10:55 ` [dpdk-dev] [PATCH v3] " Pavan Nikhilesh
2018-02-05 16:14 ` Ferruh Yigit
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=20180205104458.65f5guhfvedh2lrn@Pavan-LT \
--to=pbhagavatula@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).