From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 1FF42234 for ; Wed, 23 Mar 2016 12:53:25 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga102.jf.intel.com with ESMTP; 23 Mar 2016 04:53:24 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,382,1455004800"; d="scan'208";a="71760883" Received: from dkoncewi-mobl3.ger.corp.intel.com ([10.252.21.244]) by fmsmga004.fm.intel.com with SMTP; 23 Mar 2016 04:53:24 -0700 Received: by (sSMTP sendmail emulation); Wed, 23 Mar 2016 11:53:22 +0025 Date: Wed, 23 Mar 2016 11:53:22 +0000 From: Bruce Richardson To: Adrien Mazarguil Cc: dev@dpdk.org Message-ID: <20160323115322.GA5584@bricha3-MOBL3> References: <1458725150-13796-1-git-send-email-adrien.mazarguil@6wind.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1458725150-13796-1-git-send-email-adrien.mazarguil@6wind.com> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [PATCH] mlx5: fix packet padding macro check X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2016 11:53:26 -0000 On Wed, Mar 23, 2016 at 10:25:49AM +0100, Adrien Mazarguil wrote: > All instances of HAVE_EXP_CREATE_WQ_FLAG_RX_END_PADDING were not replaced by > HAVE_VERBS_RX_END_PADDING during a rework of the original patch, effectively > preventing this feature from being used. > > Fixes: 89ed2405447d ("mlx5: add support for HW packet padding") > > Unfortunately I did not catch this earlier (one should avoid last minute > changes). > > Bruce, since the above commit is currently only present in your tree, can > you merge this fix with it during your next rebase? I do not mind keeping > a separate fix but the commit ID will have to be updated later. Thanks. > Done. Please check resultant commit on next-net tree: http://dpdk.org/browse/next/dpdk-next-net/commit/?h=rel_16_04&id=62d20c4d1a463379c63584bee3f102699b59c036 thanks, /Bruce