From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH v4] i40e: configure MTU Date: Thu, 23 Jun 2016 14:44:43 +0100 Message-ID: <20160623134442.GJ5024@bricha3-MOBL3> References: <1463127333-10007-1-git-send-email-beilei.xing@intel.com> <1463757424-2010-1-git-send-email-beilei.xing@intel.com> <9BB6961774997848B5B42BEC655768F80E134394@SHSMSX103.ccr.corp.intel.com> <20160609142343.GC12520@bricha3-MOBL3> <20160623101333.GA5024@bricha3-MOBL3> <94479800C636CB44BD422CB454846E013A8264@SHSMSX101.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Wu, Jingjing" , "dev@dpdk.org" To: "Xing, Beilei" Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 67ED6C476 for ; Thu, 23 Jun 2016 15:45:04 +0200 (CEST) Content-Disposition: inline In-Reply-To: <94479800C636CB44BD422CB454846E013A8264@SHSMSX101.ccr.corp.intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Jun 23, 2016 at 02:37:42PM +0100, Xing, Beilei wrote: > Hi Bruce, > > > -----Original Message----- > > From: Richardson, Bruce > > Sent: Thursday, June 23, 2016 6:14 PM > > To: Wu, Jingjing > > Cc: Xing, Beilei ; dev@dpdk.org > > Subject: Re: [dpdk-dev] [PATCH v4] i40e: configure MTU > > > > On Thu, Jun 09, 2016 at 03:23:43PM +0100, Bruce Richardson wrote: > > > On Mon, May 23, 2016 at 01:33:42AM +0000, Wu, Jingjing wrote: > > > > > > > > > > > > > -----Original Message----- > > > > > From: Xing, Beilei > > > > > Sent: Friday, May 20, 2016 11:17 PM > > > > > To: Wu, Jingjing > > > > > Cc: dev@dpdk.org; Xing, Beilei > > > > > Subject: [PATCH v4] i40e: configure MTU > > > > > > > > > > This patch enables configuring MTU for i40e. > > > > > Since changing MTU needs to reconfigure queue, stop port first > > > > > before configuring MTU. > > > > > > > > > > Signed-off-by: Beilei Xing > > > > > > > > Acked-by: Jingjing Wu > > > > > > > Applied to dpdk-next-net/rel_16_07 > > > > > > /Bruce > > > > It has been brought to my attention that there were still outstanding comments > > and issues with v3 of the patch that were never resolved, therefore this patch > > may need to be reverted, as I should not have applied it > > > > Maintainers, please do not ack patches for your components if there are still > > unresolved discussion on them! Once the component maintainer acks a patch I > > should not have to go back through the whole patch history to determine if it can > > be applied or not. > > > > Sorry for inconvenience. But here's one correction, this v4 patch is acked and applied on May 23, but v3 comments are added June 17, I think Jingjing always is a responsible maintainer :) > You are indeed quite right. My apologies to Jingjing, I didn't notice the dates on the emails, and she was fully within her rights to ack the patch as she did. Thanks for pointing this out Beilei. My bad, and apologies again. Regards, /Bruce