From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Horman Subject: Re: DPDK patch backlog Date: Fri, 16 Oct 2015 10:25:01 -0400 Message-ID: <20151016142501.GA5602@hmsreliant.think-freely.org> References: <20151015144406.1aaca698@xeon-e3> <3345500.oDnpnKKuHc@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org To: Thomas Monjalon Return-path: Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58]) by dpdk.org (Postfix) with ESMTP id 239CF5A84 for ; Fri, 16 Oct 2015 16:25:11 +0200 (CEST) Content-Disposition: inline In-Reply-To: <3345500.oDnpnKKuHc@xps13> 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, Oct 16, 2015 at 10:45:23AM +0200, Thomas Monjalon wrote: > 2015-10-15 14:44, Stephen Hemminger: > > There are currently 428 patches in New state in DPDK patchwork. > > > > Thomas, could you start reducing that backlog? > > Yes > > > The simplest solution would be to merge some of the big patch series > > from Intel for the base drivers, then reviewers can focus on the other > > patches. > > That's why having a drivers/net subtree would be useful. > Agreed, a dpdk-next tree would really be the solution here. Neil