From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v3 3/7] drivers/net/bnxt new driver for
	Broadcom bnxt
Date: Thu, 21 Apr 2016 11:00:05 +0100
Message-ID: <20160421100005.GA976@bricha3-MOBL3>
References: <1456978137-98097-1-git-send-email-stephen.hurd@broadcom.com>
 <1457125528-128877-4-git-send-email-stephen.hurd@broadcom.com>
 <20160419141933.GC15456@bricha3-MOBL3>
 <CAJ9nmBZd2D1mi2va0St+vBt4_dSqPYN9qnxw6KUZx28=dXCF2Q@mail.gmail.com>
 <20160420110107.GA11120@bricha3-MOBL3>
 <CAJ9nmBbrt3Rp21vCWvHi8drMtvytO6iR+rEqpF1M6BBcKPABVA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org,
 Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hurd <stephen.hurd@broadcom.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mga01.intel.com (mga01.intel.com [192.55.52.88])
 by dpdk.org (Postfix) with ESMTP id 45A8B2BF2
 for <dev@dpdk.org>; Thu, 21 Apr 2016 12:00:10 +0200 (CEST)
Content-Disposition: inline
In-Reply-To: <CAJ9nmBbrt3Rp21vCWvHi8drMtvytO6iR+rEqpF1M6BBcKPABVA@mail.gmail.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Wed, Apr 20, 2016 at 02:32:18PM -0700, Stephen Hurd wrote:
> > It's not for testing, more for code review and to help understand the code
> > [though
> > as you say, we do need to ensure that each commit doesn't actually break
> > the
> > build].
> > Right now, the driver code goes in as a single commit - which makes it a
> > hard
> > enough task to review and see what is in there. One suggestion that
> > hopefully
> > wouldn't be too much work might be to split the code up into: basic device
> > init code, RX and TX functions, and then any additional features based on
> > top
> > of that [ideally one patch per added feature].
> >
> 
> The current driver doesn't have much beyond basic TX/RX, but we can give it
> a shot.  "Too much work" is relative of course, but splitting it into
> self-contained easily understood chunks will absolutely be a lot of work.
> 
> Adding Ajit who will also be working on this.  Since he's coming up to
> speed on the driver code, this could be a good way for him to fully
> familiarize himself with it.
> 
Sure, thanks. Any splitting you can do at all would be appreciated and help with
reviews.

/Bruce