From: Stephen Hemminger <shemminger@vyatta.com>
To: Valdis.Kletnieks@vt.edu
Cc: Kay Sievers <kay.sievers@vrfy.org>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Jiri Slaby <jslaby@suse.cz>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Greg KH <greg@kroah.com>, LKML <linux-kernel@vger.kernel.org>,
ML netdev <netdev@vger.kernel.org>
Subject: Re: network regression: cannot rename netdev twice
Date: Wed, 8 Feb 2012 12:27:56 -0800 [thread overview]
Message-ID: <20120208122756.46aa408c@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <10120.1328731572@turing-police.cc.vt.edu>
[-- Attachment #1: Type: text/plain, Size: 111 bytes --]
Our customers would prefer network device names of the form
"Ethernet0/0" or "ge-0/0/0" (but I said no...)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-08 20:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F27120A.4040106@suse.cz>
[not found] ` <CAPXgP12Sr2KzGJ9RA13QBOCkctb-z3O4+1uHOjANgMDDv2pxaQ@mail.gmail.com>
2012-01-31 10:41 ` network regression: cannot rename netdev twice Jiri Slaby
2012-01-31 10:52 ` Kay Sievers
2012-01-31 11:00 ` Jiri Slaby
2012-01-31 11:13 ` Kay Sievers
2012-01-31 11:17 ` Jiri Slaby
2012-01-31 11:58 ` Kay Sievers
2012-01-31 14:18 ` Eric W. Biederman
2012-01-31 14:40 ` [PATCH] sysfs: Update the name hash when renaming sysfs entries Eric W. Biederman
2012-01-31 14:41 ` Jiri Slaby
2012-01-31 14:55 ` Greg KH
2012-02-04 2:14 ` network regression: cannot rename netdev twice Henrique de Moraes Holschuh
2012-02-06 20:03 ` Kay Sievers
2012-02-08 2:00 ` Henrique de Moraes Holschuh
2012-02-08 3:50 ` Kay Sievers
2012-02-08 6:42 ` Valdis.Kletnieks
2012-02-08 10:57 ` Kay Sievers
2012-02-08 20:06 ` Valdis.Kletnieks
2012-02-08 20:27 ` Stephen Hemminger [this message]
2012-02-08 23:48 ` Kay Sievers
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=20120208122756.46aa408c@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=ebiederm@xmission.com \
--cc=greg@kroah.com \
--cc=hmh@hmh.eng.br \
--cc=jslaby@suse.cz \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--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).