From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by dpdk.org (Postfix) with ESMTP id 9F1AF1B1BF for ; Mon, 5 Feb 2018 12:47:02 +0100 (CET) X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Feb 2018 03:47:00 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,464,1511856000"; d="scan'208";a="171741199" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.77]) by orsmga004.jf.intel.com with SMTP; 05 Feb 2018 03:46:59 -0800 Received: by (sSMTP sendmail emulation); Mon, 05 Feb 2018 11:46:58 +0000 Date: Mon, 5 Feb 2018 11:46:58 +0000 From: Bruce Richardson To: Ferruh Yigit Cc: Pavan Nikhilesh , jerin.jacob@caviumnetworks.com, santosh.shukla@caviumnetworks.com, dev@dpdk.org Message-ID: <20180205114657.GB19776@bricha3-MOBL3.ger.corp.intel.com> References: <20180122154507.14617-1-pbhagavatula@caviumnetworks.com> <20180204153309.17312-1-pbhagavatula@caviumnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Research and Development Ireland Ltd. User-Agent: Mutt/1.9.1 (2017-09-22) Subject: Re: [dpdk-dev] [PATCH v2] net/octeontx: register fpa as platform HW mempool X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Feb 2018 11:47:03 -0000 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 > > --- > > > > 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