From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id C1C197CBA for ; Wed, 14 Mar 2018 10:08:59 +0100 (CET) X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Mar 2018 02:08:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,469,1515484800"; d="scan'208";a="211417944" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.118]) by fmsmga005.fm.intel.com with SMTP; 14 Mar 2018 02:08:55 -0700 Received: by (sSMTP sendmail emulation); Wed, 14 Mar 2018 09:08:54 +0000 Date: Wed, 14 Mar 2018 09:08:54 +0000 From: Bruce Richardson To: Hemant Agrawal Cc: dev@dpdk.org, thomas@monjalon.net Message-ID: <20180314090854.GA12092@bricha3-MOBL.ger.corp.intel.com> References: <1519889597-5805-1-git-send-email-hemant.agrawal@nxp.com> <1521014166-3201-1-git-send-email-hemant.agrawal@nxp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1521014166-3201-1-git-send-email-hemant.agrawal@nxp.com> Organization: Intel Research and Development Ireland Ltd. User-Agent: Mutt/1.9.4 (2018-02-28) Subject: Re: [dpdk-dev] [PATCH v3 00/10] meson build support for dpaaX 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: Wed, 14 Mar 2018 09:09:01 -0000 On Wed, Mar 14, 2018 at 01:25:56PM +0530, Hemant Agrawal wrote: > Earlier dpaaX was only compiled for armv8 target. This patch series first prepares the dpaaX drivers to be compiled for non-ARM platform as well. > > > Note: This patch changes all of the dpaa drivers/modules - So it shall be applied to master tree instead of meson build tree. > >>From discussion with Thomas, the proposal was for me to take this entire set into the build tree. However, if it's likely to cause conflicts with future patches from you, I can send a pull-request shortly after merge to get it into main tree too. Would that work for you? Thomas, you ok to take an early PR for next-build? /Bruce