Date: Tue, 6 Dec 2016 11:54:04 +0100
From: Greg KH <gregkh@linuxfoundation.org>
To: kys@microsoft.com
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
        olaf@aepfle.de, apw@canonical.com, vkuznets@redhat.com,
        jasowang@redhat.com, leann.ogasawara@canonical.com,
        Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH V2 15/15] hyperv: Add a function to detect if the device
 is a vmbus dev
Message-ID: <20161206105404.GA19472@kroah.com>
References: <1480797239-10085-1-git-send-email-kys@exchange.microsoft.com>
 <1480797282-10126-1-git-send-email-kys@exchange.microsoft.com>
 <1480797282-10126-15-git-send-email-kys@exchange.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1480797282-10126-15-git-send-email-kys@exchange.microsoft.com>
User-Agent: Mutt/1.7.2 (2016-11-26)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 831
Lines: 21

On Sat, Dec 03, 2016 at 12:34:42PM -0800, kys@exchange.microsoft.com wrote:
> From: Haiyang Zhang <haiyangz@microsoft.com>
> 
> On Hyper-V, every VF interface has a corresponding synthetic
> interface managed by netvsc that share the same MAC
> address. netvsc registers for netdev events to manage this
> association. Currently we use the MAC address to manage this
> association but going forward, we want to use a serial number that
> the host publishes. To do this we need functionality similar
> to dev_is_pci() for the vmbus devices. Implement such a function.
> 
> This function will be used in subsequent patches to netvsc and in the
> interest of eliminating cross tree dependencies, this patch is being
> submitted first.

As I stated before, I want to see those patches before I will take this
one...

thanks,

greg k-h