From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH 23/25] net/qede/base: semantic/formatting changes Date: Tue, 3 Jan 2017 15:40:57 +0000 Message-ID: References: <1480756289-11835-1-git-send-email-Rasesh.Mody@cavium.com> <1480756289-11835-24-git-send-email-Rasesh.Mody@cavium.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: Dept-Eng DPDK Dev To: "Mody, Rasesh" , "dev@dpdk.org" Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id ACC8437B3 for ; Tue, 3 Jan 2017 16:40:59 +0100 (CET) In-Reply-To: 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 12/31/2016 7:41 AM, Mody, Rasesh wrote: >> From: Ferruh Yigit [mailto:ferruh.yigit@intel.com] >> Sent: Friday, December 23, 2016 7:42 AM >> >> On 12/3/2016 9:11 AM, Rasesh Mody wrote: >>> This patch consists of semantic/formatting changes. It also includes >>> comment additions. >> >> As far as I can see majority of the changes are formatting, but not all. >> >> Functional changes are hard to detect in this patch, what do you think >> separating formatting/comments patches into another patch, so functional >> changes can become more visible? > > There are few of places(ecore_hw_bar_size(), ecore_get_hw_info() and ecore_init_cmd_*), where there is a bit of code refactoring. However, they are not a major change. We have tried to isolate most of the functional changes and made them part of the separate patches as fit. I think, we can include a bit of description in commit message to cover it in this patch. Please let me know if you think otherwise. I believe it is good to separate code refactoring into different patch if possible, instead of covering this in commit log. This makes functional changes easy to find in the future. In this patch hard to spot them. Thanks, ferruh > >>> >>> Signed-off-by: Rasesh Mody >>> --- >> <...>