From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 85F675323 for ; Wed, 21 Jun 2017 09:46:02 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Jun 2017 00:46:01 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,368,1493708400"; d="scan'208";a="1185151777" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by fmsmga002.fm.intel.com with ESMTP; 21 Jun 2017 00:46:01 -0700 Received: from fmsmsx113.amr.corp.intel.com (10.18.116.7) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 21 Jun 2017 00:46:00 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by FMSMSX113.amr.corp.intel.com (10.18.116.7) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 21 Jun 2017 00:46:00 -0700 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.197]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.56]) with mapi id 14.03.0319.002; Wed, 21 Jun 2017 15:45:57 +0800 From: "Wei, FangfangX" To: Thomas Monjalon , "Xu, Qian Q" CC: "ci@dpdk.org" , "Richardson, Bruce" , "O'Driscoll, Tim" Thread-Topic: [dpdk-ci] script to determine target repo (was DPDK Lab) Thread-Index: AQHSvYx3I+glk1sDKUmp247guISu6qHVH1kAgFoiQMA= Date: Wed, 21 Jun 2017 07:45:56 +0000 Message-ID: <067B569323FEB248B5CB480E1954F4346F4174FD@SHSMSX101.ccr.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA722C837C@IRSMSX108.ger.corp.intel.com> <6814152.1hysv1icOi@xps13> <82F45D86ADE5454A95A89742C8D1410E3B5DE563@shsmsx102.ccr.corp.intel.com> <1597518.RMRyGerCAR@xps> In-Reply-To: <1597518.RMRyGerCAR@xps> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZWNjZjM4NmMtNTQyZi00Njc3LTk1NjEtYjM5MjZkMzMyMDAwIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IlJNV25nTFl6Z2pQS3ppWnNKNFIrVVN2MTVQRHFUdFh2Vm42OFkzaWlFVE09In0= x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-ci] script to determine target repo (was DPDK Lab) X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jun 2017 07:46:03 -0000 Hi Thomas, What's the status about the script which determine target repo for each pat= ch set? Currently I used the rule which you told me before: "the subject prefix on = the patches should provide the hint. If the majority of the patches start w= ith "net/" then it's for next-net, and similarly for crypto. Patches with v= irtio or vhost go to that tree, etc". But I'm not sure about the 100% correct repo. Looking forward to your script. Another thing, Qian told me that you want to know the apply sequence about = many patches in one patch set. I don't apply patches with the order of patchwork id, but the names' order = about them. Such as, patchset 25081-25085, the order of patchwork id is not the correct= patches' order. http://dpdk.org/patch/25081, subject: [dpdk-dev,v2,1/5] net/qede: refactori= ng vport handling code http://dpdk.org/patch/25083, subject: [dpdk-dev,v2,2/5] net/qede: refactori= ng multi-queue implementation http://dpdk.org/patch/25084, subject: [dpdk-dev,v2,3/5] net/qede/base: upgr= ade the FW to 8.20.0.0 http://dpdk.org/patch/25082, subject: [dpdk-dev,v2,4/5] net/qede: fix VXLAN= tunnel Tx offload flag setting http://dpdk.org/patch/25085, subject: [dpdk-dev,v2,5/5] net/qede: refactor = Tx routine After download them, the patches' names are as below: http://dpdk.org/patch/25081: dpdk-dev-v2-1-5-net-qede-refactoring-vport-han= dling-code.patch http://dpdk.org/patch/25083: dpdk-dev-v2-2-5-net-qede-refactoring-multi-que= ue-implementation.patch http://dpdk.org/patch/25084: dpdk-dev-v2-3-5-net-qede-base-upgrade-the-FW-t= o-8.20.0.0.patch http://dpdk.org/patch/25082: dpdk-dev-v2-4-5-net-qede-fix-VXLAN-tunnel-Tx-o= ffload-flag-setting.patch http://dpdk.org/patch/25085: dpdk-dev-v2-5-5-net-qede-refactor-Tx-routine.p= atch So applying these patches based on the order of their names, it will be cor= rect. Best Regards Fangfang Wei -----Original Message----- From: Thomas Monjalon [mailto:thomas@monjalon.net]=20 Sent: Tuesday, April 25, 2017 2:51 PM To: Xu, Qian Q Cc: ci@dpdk.org; Richardson, Bruce ; Wei, Fangf= angX ; O'Driscoll, Tim ; = Liu, Yuanhan Subject: Re: [dpdk-ci] script to determine target repo (was DPDK Lab) 25/04/2017 08:23, Xu, Qian Q: > Thanks Thomas and Bruce for your comments. Currently we are trying to=20 > start the per patch set performance test investigation and need to know t= he Target repo for each patch set. > The goal is to get 100% correct repo to go for each patch set. It's impor= tant for the credit of the performance result.=20 > @Thomas, could you provide any script to support the auto-filter after th= e 17.05 release? Currently, we don't have the ability to make it.=20 OK, it is on my todo list. Other task: I want to check the series support in the patchwork git.