From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 1D834A046B for ; Wed, 26 Jun 2019 13:23:07 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id E3A731E20; Wed, 26 Jun 2019 13:23:06 +0200 (CEST) Received: from mx0b-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) by dpdk.org (Postfix) with ESMTP id 390ABDED for ; Wed, 26 Jun 2019 13:23:05 +0200 (CEST) Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x5QBKtO2029437; Wed, 26 Jun 2019 04:23:04 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=pfpt0818; bh=GUeJoyKThPuSW6eSPrStFJOXDMGdZLGLU1DcDeR1KSE=; b=t8Rlz5dYMq1Y7Jwctz5FBFSE5pfgN8KmfP7sv2ne32NpUNLZS8kq8DtXFK9HFznbwmPx qrSiezLkzEJ36cRXSXCkAGUy0ZCVE+QUDqXP9h9HoCMER8rydySExqFVcuGL5wQq7kuL OWG5V56Y2vkeo12dVuJiFi5TC+zMJ9NxDalA5Qw5yFVmSB2hKVFgX7NrT0rTr9pIOiSu m2bCfgsLQKAu/OJOm2nixaIyaCOFkzY4JPnl1KqG+CtJ/u7gQI5eOqrFBQUcR5dD+Q6c zWS35UJkb5fTDHYo8iYis+MX6u+kjaK/7E3AfJJuCBqqt4NK2itw5NCJIZPRIJKWdhvU 1w== Received: from sc-exch03.marvell.com ([199.233.58.183]) by mx0a-0016f401.pphosted.com with ESMTP id 2tc5ht0gtp-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 26 Jun 2019 04:23:04 -0700 Received: from SC-EXCH01.marvell.com (10.93.176.81) by SC-EXCH03.marvell.com (10.93.176.83) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 26 Jun 2019 04:23:02 -0700 Received: from NAM02-SN1-obe.outbound.protection.outlook.com (104.47.36.52) by SC-EXCH01.marvell.com (10.93.176.81) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Frontend Transport; Wed, 26 Jun 2019 04:23:02 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.onmicrosoft.com; s=selector2-marvell-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GUeJoyKThPuSW6eSPrStFJOXDMGdZLGLU1DcDeR1KSE=; b=XyGiHpYc9kE62gXp6uSLd4EYWDRhEhCetQHHgZJyaaB+VCos9GGu6OC/9y4nAh0JvOzPz1l/sTyUARhXO+jmpNgcOAMfEdn5a4AI/0fy1qy4ZPYp44MGSzmSsyXMH+J7ElVsAQmZyToy5bNkm76J67umap595Fg+MXZvGoW0NA8= Received: from MN2PR18MB3359.namprd18.prod.outlook.com (10.255.238.88) by MN2PR18MB3262.namprd18.prod.outlook.com (10.255.237.87) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2008.13; Wed, 26 Jun 2019 11:23:01 +0000 Received: from MN2PR18MB3359.namprd18.prod.outlook.com ([fe80::d890:559:2c0c:b6fc]) by MN2PR18MB3359.namprd18.prod.outlook.com ([fe80::d890:559:2c0c:b6fc%3]) with mapi id 15.20.2008.018; Wed, 26 Jun 2019 11:23:01 +0000 From: Yash Sharma To: "Tu, Lijuan" , "dts@dpdk.org" Thread-Topic: Status of Submitted Patch Thread-Index: AdUoAur+8G03AXXAT3i+RfTj3Z08CQD9CVmAAASjHgA= Date: Wed, 26 Jun 2019 11:23:01 +0000 Message-ID: References: <8CE3E05A3F976642AAB0F4675D0AD20E0BAC527B@SHSMSX101.ccr.corp.intel.com> In-Reply-To: <8CE3E05A3F976642AAB0F4675D0AD20E0BAC527B@SHSMSX101.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [114.143.185.87] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: fddbe939-33fc-4a2f-2855-08d6fa28a60d x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR18MB3262; x-ms-traffictypediagnostic: MN2PR18MB3262: x-ms-exchange-purlcount: 5 x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:9508; x-forefront-prvs: 00808B16F3 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(376002)(39860400002)(136003)(396003)(346002)(366004)(199004)(189003)(790700001)(54896002)(26005)(486006)(71200400001)(110136005)(68736007)(14454004)(73956011)(102836004)(99286004)(9686003)(6116002)(3846002)(2501003)(7696005)(6306002)(5660300002)(2906002)(236005)(74316002)(33656002)(71190400001)(53936002)(256004)(76176011)(6246003)(55016002)(606006)(6436002)(8676002)(186003)(8936002)(3480700005)(53546011)(66946007)(446003)(81166006)(66066001)(21615005)(66446008)(7736002)(76116006)(66476007)(476003)(11346002)(6506007)(64756008)(229853002)(966005)(316002)(52536014)(25786009)(478600001)(81156014)(66556008)(86362001)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR18MB3262; H:MN2PR18MB3359.namprd18.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: marvell.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: ApUA/3dxd0RTqtUfr95Sz78E5sIywbCa/CufOyPGc5eZIzNwG4vdNRUS0V19yxGQvvq7CH5kVyXvIKzfAPmQGrGerBPX9cGMHwzH4f+4VkYf/kY50pkbcnUCLNHkd2dR3ZitVQJg19k3lPXKlIwVvMYaTzJ0Hxf7cV6oH3iCnU4F2Eb701ZLfIyNGwNeffh30NU45EB/KphkBabIL0I986jofxugg9+Pds8UYehnqCfT/SKvgCqaFE8c/7uVXS7ddsg2sfuKqEIAJHBWDX5UAjAndtMJiH3vgwNNKDNEy9o2OR3JaqAi6rbeZLJdoF/tuA9886MM+hpXA3iajCu8Q0TW5mt7F68diq/3cIrMVBL3+GmHFBZZrxl/Q/gJbT+akuF9zPpVICJirg/C7KdISloBC1m4V+H5/21M24nbA74= Content-Type: multipart/alternative; boundary="_000_MN2PR18MB335955A84D1008AAD155EF8DA5E20MN2PR18MB3359namp_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: fddbe939-33fc-4a2f-2855-08d6fa28a60d X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jun 2019 11:23:01.0530 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 70e1fb47-1155-421d-87fc-2e58f638b6e0 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: ysharma@marvell.com X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR18MB3262 X-OriginatorOrg: marvell.com X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-06-26_06:, , signatures=0 Subject: Re: [dts] Status of Submitted Patch X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org Sender: "dts" --_000_MN2PR18MB335955A84D1008AAD155EF8DA5E20MN2PR18MB3359namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Thanks for your reply Lijuan, I had submitted only one patch, I suspect my = mail server was not configured properly so it didn't get past my domain and= reach dts , so the problem was on my side, my bad, I have re-sent that pat= ch and received the acknowledgement. Thanks, Yash From: Tu, Lijuan Sent: Wednesday, June 26, 2019 1:55 PM To: Yash Sharma ; dts@dpdk.org Subject: [EXT] RE: Status of Submitted Patch External Email ________________________________ Hi Yash, Sorry, currently we don't have tools like patchwork to monitor patch statu= s. You can skimpily track your patch through mail list: https://mails.dpdk.or= g/archives/dts/ , If the patch get some comments or applied, someone will r= eply to it. If you haven't received any response for a long time, you can email me, reg= ularly I work on DTS maintaining every Wednesday. BTW, I didn't get your patch except https://mails.dpdk.org/archives/dts/201= 9-June/006377.html From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Yash Sharma Sent: Friday, June 21, 2019 3:34 PM To: dts@dpdk.org Subject: [dts] Status of Submitted Patch Hi, I have submitted a patch to dts@dpdk.org using "git se= nd-email" and it's been a week, I haven't received any response. I am aware that for checking status of dpdk patches there is "http://patchw= ork.dpdk.org/". Is there any similar facility for monitoring status of DTS patches as well. Thanks, Yash --_000_MN2PR18MB335955A84D1008AAD155EF8DA5E20MN2PR18MB3359namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Thanks for your reply Lijuan, I had submitted only o= ne patch, I suspect my mail server was not configured properly so it didn&#= 8217;t get past my domain and reach dts , so the problem was on my side, my= bad, I have re-sent that patch and received the acknowledgement.

 

Thanks,

Yash

From: Tu, Lijuan <lijuan.tu@intel.com> =
Sent: Wednesday, June 26, 2019 1:55 PM
To: Yash Sharma <ysharma@marvell.com>; dts@dpdk.org
Subject: [EXT] RE: Status of Submitted Patch

 

External Email

Hi Yash,

 

Sorry, currently  we don’t have tools lik= e patchwork to monitor patch status.

You can skimpily track your patch through mail list:=  https://mails.dpdk.= org/archives/dts/ , If the patch get some comments or applied, someone = will reply to it.

If you haven’t received any response for a lon= g time, you can email me, regularly I work on DTS maintaining every Wednesd= ay.

BTW, I didn’t get your patch except https://mails.dpdk.org/archives/dts/2019-June/006377.html

 

 

 

From: dts= [mailto:dts-bounces@dpdk.org] On Behalf Of Yash Sharma
Sent: Friday, June 21, 2019 3:34 PM
To: dts@dpdk.org
Subject: [dts] Status of Submitted Patch

 

Hi,

 

I have submitted a patch to dts@dpdk.org using “git send-email” and it’s = been a week, I haven’t received any response.

I am aware that for checking status of dpdk patches = there is “http://patchwork.dpd= k.org/”.

Is there any similar facility for monitoring status = of DTS patches as well.

 

Thanks,

Yash

--_000_MN2PR18MB335955A84D1008AAD155EF8DA5E20MN2PR18MB3359namp_--