From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: netvsc NAPI patch process
Date: Thu, 26 Jan 2017 15:48:46 -0500 (EST)
Message-ID: <20170126.154846.1186219396179258597.davem@davemloft.net>
References: <20170126100405.0eac2dea@xeon-e3>
        <DM5PR03MB249073BDE0362C6A7051AA8EA0770@DM5PR03MB2490.namprd03.prod.outlook.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: stephen@networkplumber.org, greg@kroah.com, netdev@vger.kernel.org
To: kys@microsoft.com
Return-path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([184.105.139.130]:46018 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753754AbdAZV1A (ORCPT
        <rfc822;netdev@vger.kernel.org>); Thu, 26 Jan 2017 16:27:00 -0500
In-Reply-To: <DM5PR03MB249073BDE0362C6A7051AA8EA0770@DM5PR03MB2490.namprd03.prod.outlook.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

From: KY Srinivasan <kys@microsoft.com>
Date: Thu, 26 Jan 2017 20:46:40 +0000

> In the past, we have done this in two stages - get the supporting
> vmbus patches into Greg's tree first and in the next merge cycle get
> the netvsc patches in. Why not continue to do what we have done in
> the past to address cross-tree dependencies.

It takes too damn long.