From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 2584E1CDA5 for ; Thu, 5 Apr 2018 23:07:47 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A9D9C21393; Thu, 5 Apr 2018 17:07:46 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 05 Apr 2018 17:07:46 -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=1vgyhTj7KuKKxnOqhcsG0wUn11 E8Fkb0wK1WVQfclcY=; b=R/HltIR36TkoCIWpt7QWDEXgCuXFULPxzCEfrTbiBS jhqrCj1FrZX0hquqekYoPWVv/OJnoMc8JagPvz58mhB2yv093Fce5yWO7zJ6Y6r9 6ZjlelG9se0GtDKK8VO9WbEK7bCVI//LM8eC2hDxQWC+5X2ZPJuqeuF6QpIXI52o E= 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=1vgyhT j7KuKKxnOqhcsG0wUn11E8Fkb0wK1WVQfclcY=; b=W+pMHBBnXWdDW4CKqe03bg R9cw5bdpYT9nvsfhqR2oiGZC619a2DGj9gQd05qeKvTrnGvmZi2tIxHqnrjqgYag NcR2FWeRCmuDaviYaPBdo+Tz54OMnK/3FyqxmhF7ODfbwKtZyYJxdWm/ycnms69S u4cr2wIDImsAFFWZqlEIu2gdXfGqUMkNE/SM5EQ+J5TaPz7rkPypfw3Gjh5Zor1i JWbT7FRO0gvflLF8qnKEiP+jmVGZLRynSmLkYRn1LMeJsigpOyyNt5t7YLUXNgQK vskEaKzDDGKhf52EQr0vmdrJyn++31OqBR57GwE7BgRVqH/kQ7Jee4Eclk+fFrGQ == 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 20ABFE4F68; Thu, 5 Apr 2018 17:07:46 -0400 (EDT) From: Thomas Monjalon To: Stephen Hemminger Cc: Stephen Hemminger , dev@dpdk.org Date: Thu, 05 Apr 2018 23:07:45 +0200 Message-ID: <1677469.6C2FXHHyCm@xps> In-Reply-To: <20180405135946.38d4c60b@xeon-e3> References: <20180405191305.26813-1-sthemmin@microsoft.com> <8666220.g7qk7zlF1B@xps> <20180405135946.38d4c60b@xeon-e3> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 3/3] net/netvsc: add hyper-v netvsc network device 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: Thu, 05 Apr 2018 21:07:47 -0000 05/04/2018 22:59, Stephen Hemminger: > On Thu, 05 Apr 2018 22:52:31 +0200 > Thomas Monjalon wrote: > > > Hi Stephen, > > > > Good to see there is a good progress. > > > > This patch should add an entry in the release notes. > > But I guess it is not ready for 18.05? [...] > > > +The following prerequisites apply: > > > + > > > +* Linux kernel uio_hv_generic driver that supports subchannels. This should be present in 4.17 or later. > > > > The DPDK policy is to wait for prerequisite be available for merging. > > Does linux-next count? I would say no, but I could be convinced of the contrary. Can we have ABI breakage from linux-next to mainline? What is the benefit of pushing the PMD early?