From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 44C0720BD for ; Wed, 2 May 2018 23:02:16 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id DD4D022690; Wed, 2 May 2018 17:02:15 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 02 May 2018 17:02:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=LV9b9veSQgAErpyZFEx0RHH6F3 LfZ3OmMr3wPA4u//8=; b=sLW2vBdSGTl635K3bdaxMkDNRNBq4LixgyU/SIzkW9 9dtv3omgITCiyxePJW3cbv08xRRUv3cqUUVAzR9gDgM0VlaAKNQcg9IPr9vJhq79 nKhZNn1saL4WZELkHndQOZDqMCBf3DSWabAHQ+KpzSmqDLqucmbcdEQs80F7uKX9 M= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=LV9b9v eSQgAErpyZFEx0RHH6F3LfZ3OmMr3wPA4u//8=; b=URjS2BJ169FMu8FCsikR81 q0s5OP2dy60Lj7z/QzmUKveNQ2I71wuY7iAN0Cl2K1Ej1LVxGBICU1IOS3jp9ARN 0adJtJH4QKaJBoQA/J7Biguq/TmGqQ6BNTP1p5RTe72YQ0f4y9UD0R5jM2M9LKKg xacE+h538HRoUhygQf+Z5fVkw6A4Fb1mSx8TrdkmzSiXw4NH/9jR1e3fAyeZ+ItA 7/UMsyeO93nLk7gQsfGRbPKJAnNf7EhdCUbvHKsjow2KA91YXfGaf6ooAvuh8SZj tTOvxOlEdmkKNQHItsGMjX0B1ZICriPlDjjF4kJc23uSVSoqtSst2NB8x2cvRYMw == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 1F391E491A; Wed, 2 May 2018 17:02:14 -0400 (EDT) From: Thomas Monjalon To: "David Harton (dharton)" Cc: dev@dpdk.org, Yong Wang Date: Wed, 02 May 2018 23:02:12 +0200 Message-ID: <8547472.eSEYdh9Tjg@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [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 21:02:16 -0000 02/05/2018 22:38, David Harton (dharton): > 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 listing in the MAINTAINERS file but the mail bounced. The maintainer changed recently. It is Yong Wang (Cc'ed). > Is anyone familiar with the issue described in the thread above?