From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v2] net/octeontx: register fpa as platform HW
 mempool
Date: Mon, 5 Feb 2018 11:46:58 +0000
Message-ID: <20180205114657.GB19776@bricha3-MOBL3.ger.corp.intel.com>
References: <20180122154507.14617-1-pbhagavatula@caviumnetworks.com>
 <20180204153309.17312-1-pbhagavatula@caviumnetworks.com>
 <e5901329-697e-f750-f50d-c9962500e288@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>,
 jerin.jacob@caviumnetworks.com, santosh.shukla@caviumnetworks.com,
 dev@dpdk.org
To: Ferruh Yigit <ferruh.yigit@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mga18.intel.com (mga18.intel.com [134.134.136.126])
 by dpdk.org (Postfix) with ESMTP id 9F1AF1B1BF
 for <dev@dpdk.org>; Mon,  5 Feb 2018 12:47:02 +0100 (CET)
Content-Disposition: inline
In-Reply-To: <e5901329-697e-f750-f50d-c9962500e288@intel.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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.
> 
Hi Ferruh,

I disagree with this. Since the meson build is now merged into mainline,
many patches will have meson file changes to keep things building. These
patches should not go in the next-build tree but should be part of the
tree the rest of the patch targets. It should not be permitted to apply
a patch to next-net which breaks the meson build.

Only patches which add new capabilities or drivers to the build system
will go in my tree.

Regards,
/Bruce