From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by dpdk.org (Postfix) with ESMTP id DCD142C23 for ; Mon, 27 Feb 2017 13:15:08 +0100 (CET) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.15.2/8.15.1) with ESMTPS id v1RCF3bc025403 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 Feb 2017 04:15:04 -0800 (PST) Received: from ALA-MBC.corp.ad.wrs.com ([fe80::fcbe:9b7:1141:89a1]) by ALA-HCA.corp.ad.wrs.com ([147.11.189.40]) with mapi id 14.03.0294.000; Mon, 27 Feb 2017 04:15:03 -0800 From: "Legacy, Allain" To: Vincent JARDIN CC: "YIGIT, FERRUH" , "dev@dpdk.org" , "thomas.monjalon@6wind.com" , Olivier MATZ Thread-Topic: [dpdk-dev] [PATCH v2 00/16] Wind River Systems AVP PMD Thread-Index: AQHSkNchZXawOhkfI0C1CJP/QSWFnqF8wyzg Date: Mon, 27 Feb 2017 12:15:02 +0000 Message-ID: <70A7408C6E1BFB41B192A929744D85238A757B6D@ALA-MBC.corp.ad.wrs.com> References: <1487985795-136044-1-git-send-email-allain.legacy@windriver.com> <1488136143-116389-1-git-send-email-allain.legacy@windriver.com> <06f382a8-b177-fc58-945e-eab6f23639b0@6wind.com> In-Reply-To: <06f382a8-b177-fc58-945e-eab6f23639b0@6wind.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.224.140.166] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v2 00/16] Wind River Systems AVP PMD 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: Mon, 27 Feb 2017 12:15:09 -0000 > -----Original Message----- > From: Vincent JARDIN [mailto:vincent.jardin@6wind.com] ... > So, before spending too much time in reviewing your long serie, I think t= hat > proper statements are needed. In the past, other NICs using Qemu have > been sent, but they were avoided since virtio solved all the issues. >=20 Ok, I'll put together some additional information. Should I resubmit the p= atch series with an updated cover letter, update the NIC guide doc, or just= reply to this thread? So is the intent to only have a single qemu based device/driver then? If = so, why?