From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 43C262C8 for ; Tue, 13 Dec 2016 10:24:36 +0100 (CET) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga104.fm.intel.com with ESMTP; 13 Dec 2016 01:24:35 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,340,1477983600"; d="scan'208";a="41923675" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by fmsmga005.fm.intel.com with ESMTP; 13 Dec 2016 01:24:35 -0800 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 13 Dec 2016 01:24:34 -0800 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.11]) by SHSMSX104.ccr.corp.intel.com ([169.254.5.9]) with mapi id 14.03.0248.002; Tue, 13 Dec 2016 17:24:33 +0800 From: "Wei, FangfangX" To: Thomas Monjalon CC: "Mcnamara, John" , "ci@dpdk.org" , "Xu, Qian Q" , "Liu, Yong" , "Chen, WeichunX" Thread-Topic: [dpdk-ci] [PATCH v4 7/7] tests: add checkpatch Thread-Index: AQHSTvs6nSM4jn92akWd6gn3UCZF/6D6ch+A//+iiACAAeZw8P//uoEAgAHfJPD///BIgAA0CAbQ//+wh4D/+v1RYP/1vF9ggBQI6gD//gPW4ABvbWaA//94KFA= Date: Tue, 13 Dec 2016 09:24:32 +0000 Message-ID: <067B569323FEB248B5CB480E1954F4346E9CD7E6@SHSMSX103.ccr.corp.intel.com> References: <1480599892-14190-1-git-send-email-thomas.monjalon@6wind.com> <2218616.KkapDu6pJP@xps13> <067B569323FEB248B5CB480E1954F4346E9CD7AD@SHSMSX103.ccr.corp.intel.com> <15275169.NpaZ2izZKq@xps13> In-Reply-To: <15275169.NpaZ2izZKq@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMjE4MjJhZDctNDhmMS00MTgxLTk1YjEtNGVkZDllNGEwZDI4IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6Ik5YUnNLVUZIdHVieW9rQW8raE9QWThkakJ0M1V1NGZYeE13QTlNbTR5RmM9In0= x-ctpclassification: CTP_IC 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] [PATCH v4 7/7] tests: add checkpatch 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: Tue, 13 Dec 2016 09:24:36 -0000 >> > About the title: >> > [dpdk-test-report] |SUCCESS| pw17860 [PATCH, v2] vmxnet3: fix Rx deadl= ock >> > Please remove the patchwork id pw17860, and remove the comma in [PATCH= , v2]. >>=20 >> I have remove the comma.=20 >> For the patchwork id "pw17860", I think it would be better to be remaine= d. Because if it's removed from the subject, receivers can't be directly to= ld which patch has been complicated, they must open the email to check it.= =20 >I don't understand. >With the title "|SUCCESS| [PATCH v2] vmxnet3: fix Rx deadlock]", the recei= ver see which patch was tested, isn't it? I mean if removed patchwork id, the receiver know one patch was tested, but= they don't see the patch id unless open the email. But we need the patchwork id for two reasons: 1. For debug, I want to see if the patches were tested in case of leakage t= ested. 2. We summary the tested patches status weekly. It is intuitive to see the = patchwork id in subject. Best Regards Fangfang Wei