From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: DPDK patch backlog
Date: Wed, 21 Oct 2015 10:25:12 +0200
Message-ID: <2717598.bIV87FGGpb@xps13>
References: <20151015144406.1aaca698@xeon-e3> <20151020213424.696541ad@xeon-e3>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org
To: Stephen Hemminger <stephen@networkplumber.org>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com
 [209.85.212.179]) by dpdk.org (Postfix) with ESMTP id 2E18B924B
 for <dev@dpdk.org>; Wed, 21 Oct 2015 10:26:17 +0200 (CEST)
Received: by wicfx6 with SMTP id fx6so79767970wic.1
 for <dev@dpdk.org>; Wed, 21 Oct 2015 01:26:17 -0700 (PDT)
In-Reply-To: <20151020213424.696541ad@xeon-e3>
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>

2015-10-20 21:34, Stephen Hemminger:
> Patch backlog is not getting better, now at 486.
> 
> How can we break this logjam?
> Do I need to make a new "ready for merge" tree?

What would mean "ready for merge"?
A lot of patches are acked but do not compile or doc is missing.

I have the feeling it would become easier if there were mailing-list, patchwork
and git tree dedicated to some areas. What about starting with drivers/net?