From: Thomas F Herbert <therbert@redhat.com>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK: Proposal for a patch patch-test integration tree
Date: Wed, 27 May 2015 18:36:02 -0400 [thread overview]
Message-ID: <556646D2.9020702@redhat.com> (raw)
In-Reply-To: <20150527210624.GA15347@mhcomputing.net>
On 5/27/15 5:06 PM, Matthew Hall wrote:
> On Wed, May 27, 2015 at 04:48:47PM -0400, Thomas F Herbert wrote:
>> Submissions of test suites will be encouraged from the community including
>> testing against compilers, architectures, devices, options etc. The purpose
>> is to try to evolve to widen test coverage for submitted patches.
>
> Hi Thomas,
>
> This overall idea is extremely awesome and will help me a lot so I won't have
> to try and sit there yanking in random patches from email threads.
Thanks!
In the meantime, you can yank patches from
http://dpdk.org/dev/patchwork/project/dpdk/list/ which might be easier
then sorting through the emails depending on your email client.
>
> I am not sure if it will be possible or not, but I'd like to see some test
> suites against some applications as well. They do more complex operations in
> my experience than the operations the DPDK tests do.
I will accept submitted test suites toward this goal if you would like
to write a test suite.
>
> Perhaps something like an L4-L7 firewall app or an IDS / IPS app or an L3-L4
> cloud switch / router app. Etc.
>
> Matthew.
>
next prev parent reply other threads:[~2015-05-27 22:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 20:48 Thomas F Herbert
2015-05-27 21:22 ` Vincent JARDIN
2015-05-28 14:18 ` Thomas F Herbert
[not found] ` <20150527210624.GA15347@mhcomputing.net>
2015-05-27 22:36 ` Thomas F Herbert [this message]
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=556646D2.9020702@redhat.com \
--to=therbert@redhat.com \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).