From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by dpdk.org (Postfix) with ESMTP id C3FB91E2F for ; Wed, 2 May 2018 22:38:49 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4112; q=dns/txt; s=iport; t=1525293529; x=1526503129; h=from:to:subject:date:message-id:mime-version; bh=5YGwhqIBgdE+SiQRewBEM8/tudWu4mjTu7JHJv/X1Lk=; b=d6Vxa4HGO2DSw+E65FZsCV76S3rTC1fOzunlf95E/7O/RyLItTkRPAR0 DaKBJX9xQIDdVKZlgm57lhVYV2nV1qJMpmB+DT4tEhKVAlr4yRPOcP55n fVWo//9jGB7eCWwDyQj9UB7Qg3akcNW/85x6rNCXSHR0bsBPPvakwUz29 A=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AlAQC4IOpa/49dJa1cGgEBAQEBAgE?= =?us-ascii?q?BAQEIAQEBAYJNdmEXYygKi2WMb4MDjiqEcIF4CyOHTiE0GAECAQEBAQEBAmw?= =?us-ascii?q?cAQuFXF4BgQAmAQQbhCNkD6tOiECCQogbgVQ/hysDgT8BAYVyApgUCAKFYoh?= =?us-ascii?q?fgXmKZ4k+hDuCHwIREwGBJAEcOIFScBVIFYIhCYsHhT5vjg6BH4EYAQE?= X-IronPort-AV: E=Sophos;i="5.49,354,1520899200"; d="scan'208,217";a="389770271" Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 May 2018 20:38:48 +0000 Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id w42Kcmjg018578 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Wed, 2 May 2018 20:38:48 GMT Received: from xch-rcd-016.cisco.com (173.37.102.26) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 2 May 2018 15:38:47 -0500 Received: from xch-rcd-016.cisco.com ([173.37.102.26]) by XCH-RCD-016.cisco.com ([173.37.102.26]) with mapi id 15.00.1320.000; Wed, 2 May 2018 15:38:48 -0500 From: "David Harton (dharton)" To: "dev@dpdk.org" Thread-Topic: vmxnet3 Maintainer? Thread-Index: AdPiVTWseU/SUeWORUSHC8TMLMTApg== Date: Wed, 2 May 2018 20:38:47 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.150.24.86] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] vmxnet3 Maintainer? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 May 2018 20:38:50 -0000 I've encountered a couple scenarios with vmxnet3 (dpdk 2.2 and 16.07) that = look pretty much identical to this: http://dpdk.org/ml/archives/users/2016-October/001063.html Do we have a maintainer for the vmxnet3 driver? I tried emailing the one l= isting in the MAINTAINERS file but the mail bounced. Is anyone familiar with the issue described in the thread above? Thanks, Dave