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 8BF5A2BB3 for ; Wed, 7 Dec 2016 06:49:03 +0100 (CET) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga102.jf.intel.com with ESMTP; 06 Dec 2016 21:49:01 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,310,1477983600"; d="scan'208";a="39793750" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by fmsmga005.fm.intel.com with ESMTP; 06 Dec 2016 21:49:01 -0800 Received: from fmsmsx111.amr.corp.intel.com (10.18.116.5) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 6 Dec 2016 21:49:01 -0800 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by fmsmsx111.amr.corp.intel.com (10.18.116.5) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 6 Dec 2016 21:49:01 -0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.239]) by SHSMSX103.ccr.corp.intel.com ([169.254.4.96]) with mapi id 14.03.0248.002; Wed, 7 Dec 2016 13:48:56 +0800 From: "Wei, FangfangX" To: Thomas Monjalon CC: "ci@dpdk.org" , "Xu, Qian Q" , "Liu, Yong" Thread-Topic: [dpdk-ci] [PATCH v4 7/7] tests: add checkpatch Thread-Index: AQHSTvs6nSM4jn92akWd6gn3UCZF/6D6ch+A//+iiACAAeZw8A== Date: Wed, 7 Dec 2016 05:48:55 +0000 Message-ID: <067B569323FEB248B5CB480E1954F4346BE93B58@SHSMSX101.ccr.corp.intel.com> References: <1480599892-14190-1-git-send-email-thomas.monjalon@6wind.com> <1480944373-10233-8-git-send-email-thomas.monjalon@6wind.com> <067B569323FEB248B5CB480E1954F4346BE93510@SHSMSX101.ccr.corp.intel.com> <2176771.oGMe6QWu86@xps13> In-Reply-To: <2176771.oGMe6QWu86@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYjRjZWMyZDktOTUzYi00NzU5LWE5NDEtNmYzMTJlYzY2Nzk4IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6ImplRm93UFNTXC94eUlVcXVGaGNnZUJZdm9qdE1RQlA5RmlGXC9hWDc1S2phST0ifQ== 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: Wed, 07 Dec 2016 05:49:04 -0000 Hi Thomas, I try to use " send-patch-report.sh" with your suggestion, but after run it= , nothing happened. The command shows as below: echo $report | tools/send-patch-report.sh -t "[PATCH, v3] net/i40evf: fix r= eporting of imissed packets" -f "tcrugnale@sandvine.com" -m "1481055381-142= 43-1-git-send-email-tcrugnale@sandvine.com" -p "dev.dpdk.org" -l "Intel Per= -patch compilation check" -s "SUCCESS" -d "Compilation OK" In case it was detected as a private patch, I also try to run it with my em= ail address: -f "fangfangx.wei@intel.com", nothing happened, and I didn't r= eceive this email either. Is there still any error when I use the script? (BTW: This is the report ab= out patch 17720) Best Regards Fangfang Wei -----Original Message----- From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]=20 Sent: Tuesday, December 6, 2016 4:40 PM To: Wei, FangfangX Cc: ci@dpdk.org; Xu, Qian Q ; Liu, Yong Subject: Re: [dpdk-ci] [PATCH v4 7/7] tests: add checkpatch Hi Fangfang, 2016-12-06 06:34, Wei, FangfangX: > Hi Thomas, >=20 > Here are some questiones about your scripts: >=20 > 1. With the script "send-patch-report.sh", Can I send my perpatch build r= esults to patchwork as checkpatch result in patchwork? >=20 > Such as, generate the GUI as blow: >=20 > [cid:image001.png@01D24FCC.01E4A4D0] Yes, your report will be properly integrated into patchwork if you use send= -patch-report.sh. > 2. Must I create /etc/dpdk/ci.config before using your scripts? No it is not required. > Because when I run it, it prompted following error message: > /root/dpdk-cii/tools/load-ci-config.sh: line 5: /etc/dpdk/ci.config: N= o such file or directory > /root/dpdk-cii/tools/load-ci-config.sh: line 6:=20 > /etc/dpdk/ci.config: No such file or directory It is strange. This configuration file is read only if it exists: test ! -r /etc/dpdk/ci.config || . /etc/dpdk/ci.config > 3. Some confuse about the parameters in "send-patch-report.sh": >=20 > options: > -t title subject of the patch email > -f from sender of the patch email > -m msgid id of the patch email > -p listid mailing list publishing the patch These 4 options can be filled with the help of parse-email.sh. > -l label title of the test > -s status one of these test results: SUCCESS, WARNING, = FAILURE > -d desc few words to better describe the status >=20 > For example, about patch=20 > http://www.dpdk.org/dev/patchwork/patch/17673/ >=20 > -t title subject of the patch email > Is it "[dpdk-dev,2/8] drivers/common/dpaa2: Sample descriptors for NXP= DPAA2 SEC operations."? It should be the original subject from the email, not the one converted by = patchwork (as above): [dpdk-dev] [PATCH 2/8] drivers/common/dpaa2: Sample descriptors for NXP DP= AA2 SEC operations. > -f from sender of the patch email > Is it the author who send the patch? In patch 17673, is it akhil.goyal= @nxp.com? Not exactly. You should refer to the original mail: Akhil Goyal > -m msgid id of the patch email > Is it the message-id of this patch? In patch 17673, is it 201612051255= 40.6419-3-akhil.goyal@nxp.com? No it is <20161205125540.6419-3-akhil.goyal@nxp.com> > -p listid mailing list publishing the patch > Is it the receiver about this patch? In patch 17673, is it dev@dpdk.or= g? No, it is the List-Id header: DPDK patches and discussions > I try to send my result with script "send-patch-report.sh" with below com= mand, but nothing happened. >=20 > echo "$report" | /root/dpdk-cii/tools/send-patch-report.sh -t "[dpdk-dev,= 2/8] drivers/common/dpaa2: Sample descriptors for NXP DPAA2 SEC operations.= " -f "akhil.goyal@nxp.com" -m "20161205125540.6419-3-akhil.goyal@nxp.com" -= p "dev@dpdk.org" -l "Intel Per-patch compilation check" -s "SUCCESS" -d "Co= mpilation OK" The list-id is wrong so it was detected as a private patch. It has probably sent a private report to Akhil. I think your issue is to get the original email. If I understand well, you are getting the patch from patchwork. If you want to continue getting the patch from patchwork, you must use this= URL: http://www.dpdk.org/dev/patchwork/patch/17673/mbox/ and fake listid and from. For the listid, you can use -p dev.dpdk.org For the from, you must convert = [dpdk-dev,v2,1/4] to [dpdk-dev] [PATCH v2 1/4] or just [PATCH v2 1/4] (with= out [dpdk-dev]) would be sufficient. For the checkpatch example, it fetches emails from patchwork@dpdk.org mailb= ox which is registered in the dev mailing list.