From: Remy Horton <remy.horton@intel.com>
To: Shepard Siegel <shepard.siegel@atomicrules.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Best Practices for PMD Verification before Upstream Requests
Date: Fri, 4 Nov 2016 13:41:06 +0800 [thread overview]
Message-ID: <ec939eef-7302-e2ce-30d7-51ba36957f61@intel.com> (raw)
In-Reply-To: <CAMMLSKAr+drh0NDimAoZN=9oT2zmnVsthnwhD5tEMY2kE6iMGw@mail.gmail.com>
On 02/11/2016 20:21, Shepard Siegel wrote:
[..]
> Almost a year into our DPDK development, we have shipped an alpha version
> of our "Arkville" product. We've thankful for all the support from this
> Most everyone has suggested "get your code upstream ASAP"; but our
> team is cut from the "if it isn't tested, it doesn't work" cloth. We now
> have some solid miles on our Arkville PMD driver "ark" with 16.07. Mostly
> testpmd and a suite of user apps; dts not so much, only because our use
> case is a little different.
To me that sounds good enough for a v1 patch.
> One question that
> came up is "Should we do a thorough port and regression against 16.11 as a
> precursor to up streaming at 17.02?". Constructive feedback always welcome!
It is helpful, although bear in mind there is only so much you'll be
able to test. Patches sent to the mailing list are picked up by
patchwork for automated testing, so you'll find out quite quickly if
you've broken something.
And avoid top-posting.. :)
..Remy
prev parent reply other threads:[~2016-11-04 5:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 12:34 Shepard Siegel
2016-08-22 13:07 ` Thomas Monjalon
2016-11-02 12:21 ` Shepard Siegel
2016-11-04 5:41 ` Remy Horton [this message]
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=ec939eef-7302-e2ce-30d7-51ba36957f61@intel.com \
--to=remy.horton@intel.com \
--cc=dev@dpdk.org \
--cc=shepard.siegel@atomicrules.com \
--cc=thomas.monjalon@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 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).