From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: Re: [PATCH v2] hv_netvsc: automatically name slave VF network
 device
Date: Tue, 19 Dec 2017 16:02:59 -0800
Message-ID: <20171219160259.69ad98dc@cakuba.netronome.com>
References: <20171219235930.16916-1-sthemmin@microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: netdev@vger.kernel.org, Stephen Hemminger <sthemmin@microsoft.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Return-path: <netdev-owner@vger.kernel.org>
Received: from mail-qt0-f181.google.com ([209.85.216.181]:40266 "EHLO
        mail-qt0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752656AbdLTADD (ORCPT
        <rfc822;netdev@vger.kernel.org>); Tue, 19 Dec 2017 19:03:03 -0500
Received: by mail-qt0-f181.google.com with SMTP id u42so26368064qte.7
        for <netdev@vger.kernel.org>; Tue, 19 Dec 2017 16:03:03 -0800 (PST)
In-Reply-To: <20171219235930.16916-1-sthemmin@microsoft.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On Tue, 19 Dec 2017 15:59:30 -0800, Stephen Hemminger wrote:
> Rename the VF device to ethX_vf based on the ethX as the
> synthetic device.  This eliminates the need for delay on setup,
> and the PCI (udev based) naming is not reproducible on Hyper-V
> anyway. The name of the VF does not matter since all control
> operations take place the primary device. It does make the
> user experience better to associate the names.
> 
> Based on feedback from all.systems.go talk.
> 
> Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>

I think you must have hit send before seeing my last reply on v1...