From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2 04/22] qede/base: update base driver Date: Wed, 05 Oct 2016 18:29:20 +0200 Message-ID: <2423952.d1lHHhMD9K@xps13> References: <1475219169-8774-1-git-send-email-rasesh.mody@qlogic.com> <1ac6d74c-cc78-4efd-275c-9645952fb8a0@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Ferruh Yigit , Rasesh Mody , dev@dpdk.org, "Dept-EngDPDKDev@qlogic.com" , Bruce Richardson To: "Mody, Rasesh" Return-path: Received: from mail-wm0-f51.google.com (mail-wm0-f51.google.com [74.125.82.51]) by dpdk.org (Postfix) with ESMTP id F32552931 for ; Wed, 5 Oct 2016 18:29:24 +0200 (CEST) Received: by mail-wm0-f51.google.com with SMTP id k125so276980283wma.1 for ; Wed, 05 Oct 2016 09:29:24 -0700 (PDT) In-Reply-To: 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" 2016-09-30 18:40, Mody, Rasesh: > > From: Ferruh Yigit [mailto:ferruh.yigit@intel.com] > > Thank you for the update, base driver patch update now reduced from > > "14653 insertions(+), 8536 deletions(-)" to > > "10857 insertions(+), 4853 deletions(-)" > > > > But this is still to big for reviewing, specially there are some low hanging fruits > > for cleanup, like big chunk of comment updates or whitespace updates or > > non base driver codes in the patch. > > > > If the expectation is that somebody non maintainer review the code, > > understand it and highlight any possible defects, I believe this patch is too big > > and needs to be split more into logical pieces, but since this is a driver code > > and a little special, and it may not be possible to completely understand the > > code without knowing underlying hardware, I am not sure how to proceed > > and adding Bruce and Thomas to cc for guidance. As you said it makes contribution really hard. So it is missing the point of sharing its source code in Open Source. > This 8.10.x.x base driver is a common code shared by multiple drivers. It has gone through extensive testing. > We have split the base driver patch into smaller logical patches. It would be difficult to split this patch further. Please check how Intel updates its base drivers and try harder. We all know it requires some time, but it provides a valuable knowledge base. Thanks