From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 413032C45 for ; Fri, 4 Nov 2016 06:41:09 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga103.fm.intel.com with ESMTP; 03 Nov 2016 22:41:08 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,442,1473145200"; d="scan'208";a="782261168" Received: from rhorton-mobl.ger.corp.intel.com (HELO [172.16.225.75]) ([172.16.225.75]) by FMSMGA003.fm.intel.com with ESMTP; 03 Nov 2016 22:41:07 -0700 To: Shepard Siegel , Thomas Monjalon References: <2866322.PnTaiuzzpn@xps13> Cc: dev@dpdk.org From: Remy Horton Organization: Intel Shannon Limited Message-ID: Date: Fri, 4 Nov 2016 13:41:06 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] Best Practices for PMD Verification before Upstream Requests X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2016 05:41:09 -0000 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