From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v2] enic flow director fixes Date: Thu, 9 Feb 2017 12:15:21 +0000 Message-ID: <2a7ba108-ddd4-acf7-cba3-bc6c9cb4716b@intel.com> References: <20170203095446.4614-1-johndale@cisco.com> <20170209004009.26242-1-johndale@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: dev@dpdk.org To: John Daley Return-path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id E5E94BD2A for ; Thu, 9 Feb 2017 13:15:23 +0100 (CET) In-Reply-To: <20170209004009.26242-1-johndale@cisco.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 2/9/2017 12:40 AM, John Daley wrote: > This should replace > http://www.dpdk.org/dev/patchwork/patch/20147/ which was an intermediate patch > in a small patchset and had a compile error. Also, please reject the 2nd patch > in the patchset http://www.dpdk.org/dev/patchwork/patch/20148/ which is > incomplete. I will change the state of these patches in patchworks. > thank you, john Hi John, I dropped the previous two and will get this one. And this looks like the squashed version of the previous two with some updates in ipv6 shift number. Although next-net can re-write the git history, this is mainly to provide ability to rebasing on master tree. Not for amending patches on fly, that is confusing. Please next time do not rely on git history re-writing while sending patches. Thanks, ferruh > > John Daley (1): > net/enic: fix hardcoding of some flow director masks > > drivers/net/enic/enic_clsf.c | 14 +++++++------- > 1 file changed, 7 insertions(+), 7 deletions(-) >