From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id D4B715689 for ; Thu, 22 Sep 2016 08:34:40 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga101.fm.intel.com with ESMTP; 21 Sep 2016 23:34:39 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,378,1470726000"; d="scan'208";a="1034544258" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by orsmga001.jf.intel.com with ESMTP; 21 Sep 2016 23:34:40 -0700 Received: from fmsmsx101.amr.corp.intel.com (10.18.124.199) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.248.2; Wed, 21 Sep 2016 23:34:39 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by fmsmsx101.amr.corp.intel.com (10.18.124.199) with Microsoft SMTP Server (TLS) id 14.3.248.2; Wed, 21 Sep 2016 23:34:38 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.234]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.96]) with mapi id 14.03.0248.002; Thu, 22 Sep 2016 14:34:36 +0800 From: "Liu, Yong" To: Thomas Monjalon , "De Lara Guarch, Pablo" , Stephen Finucane CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] DPDK patchwork upgrade Thread-Index: AQHSCRjGCIRzRlhWRkiBocuZdXE6EaBttK4AgAAGDYCAF2aJMA== Date: Thu, 22 Sep 2016 06:34:36 +0000 Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E602DDBC0@SHSMSX103.ccr.corp.intel.com> References: <1736050.3Z5tnqk6B6@xps13> <9398822.xtO6cvAGR1@xps13> In-Reply-To: <9398822.xtO6cvAGR1@xps13> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNzI0MmQ4YWQtZDJkMi00NTA5LWJhMTQtY2YwNzllNjk5NzQyIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IjJYUWVyNjRZd1Vudkc1SzBQZ3ZDeVVuU2dQdXRFeXNFdlJOdE04dUZrcEk9In0= 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-dev] DPDK patchwork upgrade 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: Thu, 22 Sep 2016 06:34:41 -0000 Thomas, There's another new column "S/W/F" added in latest patchwork. This column i= s represent for validation status "success/warning/failure". At last the status will be stored into patchwork_check database and used fo= r continuous integration. Below is just one sample for check infor. Do you have any plan to implement= it in dpdk validation process? ./patchwork/bin/pwclient check-info 1 Information for check id 1 -------------------------- - context : stv-test - date : 2016-09-22 23:51:07.476802 - description : test report from STV team - id : 1 - patch : Add sqlparse to production requirements. - patch_id : 1077 - state : success - target_url : N/A - user : root - user_id : 1 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon > Sent: Thursday, September 08, 2016 1:02 AM > To: De Lara Guarch, Pablo; Stephen Finucane > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] DPDK patchwork upgrade >=20 > 2016-09-07 16:40, De Lara Guarch, Pablo: > > I am looking at it, and I see two issues: > > - There are some patches that have been acked, but I don't see that in > patchwork > > (e.g. http://dpdk.org/dev/patchwork/patch/15381/) >=20 > Yes the new columns are empty. > I guess they will be filled starting from now. > Stephen, could we re-parse old emails (from August/September) to fill > A/R/T without breaking the database? >=20 > > - Is there any way to see if patches in a patchset have been acked? > > Usually, patchsets are acked by replying to the cover letter, > > but this is not going to be reflected in Patchwork, correct? >=20 > Yes, I think the next version of patchwork will support series > and cover letter parsing. >=20 > Maybe we could also be able to check the message id of a previous > cover letter before sending a new version of a series?