netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Hank Janssen <hjanssen@microsoft.com>
Cc: Greg KH <gregkh@suse.de>, netdev@vger.kernel.org
Subject: [PATCH] hv: name network device ethX rather than sethX
Date: Thu, 11 Mar 2010 09:11:37 -0800	[thread overview]
Message-ID: <20100311091137.27f22c57@nehalam> (raw)
In-Reply-To: <20100309174217.00ae3f3b@nehalam>

This patch makes the HyperV network device use the same naming
scheme as other virtual drivers (Xen, KVM). In an ideal world, 
userspace tools would not care what the name is, but some 
users and applications do care. Vyatta CLI is one of the tools
that does depend on what the name is.

Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
---
 drivers/staging/hv/netvsc_drv.c |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

--- a/drivers/staging/hv/netvsc_drv.c	2010-03-09 17:34:45.012686682 -0800
+++ b/drivers/staging/hv/netvsc_drv.c	2010-03-11 09:08:00.480877949 -0800
@@ -381,8 +381,7 @@ static int netvsc_probe(struct device *d
 	if (!net_drv_obj->Base.OnDeviceAdd)
 		return -1;
 
-	net = alloc_netdev(sizeof(struct net_device_context), "seth%d",
-			   ether_setup);
+	net = alloc_etherdev(sizeof(struct net_device_context));
 	if (!net)
 		return -1;
 

  reply	other threads:[~2010-03-11 17:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AD02C96F1FB40A4B896D24F974E9B9D42AA4787A@TK5EX14MBXC139.redmond.corp.microsoft.com>
     [not found] ` <20100308154549.1c62a33b@nehalam>
     [not found]   ` <8AFC7968D54FB448A30D8F38F259C5621AF725A9@TK5EX14MBXC116.redmond.corp.microsoft.com>
     [not found]     ` <20100309173855.7d297c44@nehalam>
2010-03-10  1:42       ` [PATCH 2/2] hv: handle skb allocation failure Stephen Hemminger
2010-03-11 17:11         ` Stephen Hemminger [this message]
2010-03-10  1:42     ` [PATCH 1/2] hv: use network device stats Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100311091137.27f22c57@nehalam \
    --to=shemminger@vyatta.com \
    --cc=gregkh@suse.de \
    --cc=hjanssen@microsoft.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).