From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pmatilai@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by dpdk.org (Postfix) with ESMTP id 9F8379378
 for <dev@dpdk.org>; Wed, 21 Oct 2015 10:48:15 +0200 (CEST)
Received: from int-mx14.intmail.prod.int.phx2.redhat.com
 (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27])
 by mx1.redhat.com (Postfix) with ESMTPS id 06EA4461D4;
 Wed, 21 Oct 2015 08:48:15 +0000 (UTC)
Received: from dhcp195.koti.laiskiainen.org (vpn1-6-228.ams2.redhat.com
 [10.36.6.228])
 by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id
 t9L8mDKa005384; Wed, 21 Oct 2015 04:48:14 -0400
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
 Stephen Hemminger <stephen@networkplumber.org>
References: <20151015144406.1aaca698@xeon-e3>
 <20151020213424.696541ad@xeon-e3> <2717598.bIV87FGGpb@xps13>
From: Panu Matilainen <pmatilai@redhat.com>
Message-ID: <5627514D.1010103@redhat.com>
Date: Wed, 21 Oct 2015 11:48:13 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <2717598.bIV87FGGpb@xps13>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK patch backlog
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
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>
X-List-Received-Date: Wed, 21 Oct 2015 08:48:15 -0000

On 10/21/2015 11:25 AM, Thomas Monjalon wrote:
> 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.

Well, isn't that one quite reasonable definition of being "ready"?
- patch must be acked
- patch must apply and compile (when relevant)
- is appropriately documented (commit message style and all)

- Panu -

>
> 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?
>