From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH v2 0/6] ena: update PMD to cooperate with latest ENA firmware Date: Wed, 29 Jun 2016 12:01:40 +0100 Message-ID: <20160629110139.GC3624@bricha3-MOBL3> References: <1466099690-28085-1-git-send-email-jan@semihalf.com> <1466510763-19569-1-git-send-email-jan@semihalf.com> <20160624115239.GI13456@bricha3-MOBL3> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org, ferruh.yigit@intel.com To: Jan Medala Return-path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 162562BA9 for ; Wed, 29 Jun 2016 13:01:45 +0200 (CEST) Content-Disposition: inline In-Reply-To: <20160624115239.GI13456@bricha3-MOBL3> 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 Fri, Jun 24, 2016 at 12:52:39PM +0100, Bruce Richardson wrote: > On Tue, Jun 21, 2016 at 02:05:57PM +0200, Jan Medala wrote: > > As requested, big patch splitted into logical pieces for easier review. > > Improved style and fixed icc compiler issues. > > > > Thanks for the patch split. However, many of the patches don't have a commit > message describing (at a high level), what the goal of that patch is and how > it goes about implementing the changes to achieve that goal. Can you add a > paragraph or two of commit message to each patch on the set to help anyone > looking at the code understand what is happening in each patch. > > Regards, > /Bruce > Any update on this set? Is a V3 coming for 16.07 timeframe? /Bruce