From mboxrd@z Thu Jan 1 00:00:00 1970 From: "David Harton (dharton)" Subject: vmxnet3 Maintainer? Date: Wed, 2 May 2018 20:38:47 +0000 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable To: "dev@dpdk.org" 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) 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 Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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