From: Thomas F Herbert <therbert@redhat.com>
To: Vincent JARDIN <vincent.jardin@6wind.com>, dev@dpdk.org
Subject: Re: DPDK: Proposal for a patch patch-test integration tree
Date: Thu, 28 May 2015 10:18:40 -0400 [thread overview]
Message-ID: <556723C0.8060709@redhat.com> (raw)
In-Reply-To: <5566359B.6050408@6wind.com>
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
next prev parent reply other threads:[~2015-05-28 14:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 20:48 DPDK: Proposal for a patch patch-test integration tree Thomas F Herbert
2015-05-27 21:22 ` Vincent JARDIN
2015-05-28 14:18 ` Thomas F Herbert [this message]
[not found] ` <20150527210624.GA15347@mhcomputing.net>
2015-05-27 22:36 ` Thomas F Herbert
2015-05-28 6:54 ` Simon Kågström
2015-05-28 13:10 ` Wiles, Keith
2015-05-28 9:48 ` Thomas Monjalon
[not found] ` <556728A1.8070403@redhat.com>
2015-05-28 14:44 ` Thomas Monjalon
2015-05-28 15:01 ` Thomas F Herbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=556723C0.8060709@redhat.com \
--to=therbert@redhat.com \
--cc=dev@dpdk.org \
--cc=vincent.jardin@6wind.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.