From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <therbert@redhat.com> Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 6E9085A50 for <dev@dpdk.org>; Thu, 28 May 2015 16:18:33 +0200 (CEST) Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (Postfix) with ESMTPS id A5A2D337676; Thu, 28 May 2015 14:18:32 +0000 (UTC) Received: from [10.10.56.66] (vpn-56-66.rdu2.redhat.com [10.10.56.66]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t4SEIVqt004500; Thu, 28 May 2015 10:18:32 -0400 Message-ID: <556723C0.8060709@redhat.com> Date: Thu, 28 May 2015 10:18:40 -0400 From: Thomas F Herbert <therbert@redhat.com> Organization: Red Hat User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Vincent JARDIN <vincent.jardin@6wind.com>, dev@dpdk.org References: <55662DAF.3000909@redhat.com> <5566359B.6050408@6wind.com> In-Reply-To: <5566359B.6050408@6wind.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.22 Subject: Re: [dpdk-dev] DPDK: Proposal for a patch patch-test integration tree 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: Thu, 28 May 2015 14:18:33 -0000 On 5/27/15 5:22 PM, Vincent JARDIN wrote: > On 27/05/2015 22:48, Thomas F Herbert wrote: >> Work Flow and Process: >> >> All patches will be taken from from public submissions to dpdk-dev.org >> scraped from dpdk patchwork. Patches will be applied to the patch-test >> tree and tested against HEAD as they are received. The feedback from the >> testing will be provided to the community. The patch-test tree will >> periodically be git pull'ed from dpdk. >> >> Longer term goal: >> >> Initially, the patches will be applied along with some simple smoke >> tests. The longer term goal is to automate this process, apply more >> extensive tests and post the results in dpdk patchwork, >> http://dpdk.org/dev/patchwork/project/dpdk/list/ which would have an >> accompanying mailing list for distribution of a results summary of the >> tests. > > thanks for helping. > > It could be broken into two parts: > - patch-test-net-next, > http://dpdk.org/browse/dpdk/tree/MAINTAINERS#n190 > http://dpdk.org/browse/dpdk/tree/drivers/net > > - patch-test-other-next, > all, excepted drivers Vincent, I don't understand what is in patch-test-next vs patch-test-other-next. Is patch-test-other-next to be for pmd drivers that are not included in the standard dpdk release? > > Best regards, > Vincent