From: Rick Jones <rick.jones2@hp.com>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: linux-hotplug@vger.kernel.org, netdev@vger.kernel.org,
narendra_k@dell.com, jcm@redhat.com, notting@redhat.com
Subject: Re: extended netdevice naming proposal
Date: Thu, 18 Nov 2010 18:34:29 +0000 [thread overview]
Message-ID: <4CE571B5.9070600@hp.com> (raw)
In-Reply-To: <20101117220659.GA12177@auslistsprd01.us.dell.com>
With the presence of the pci_slot driver to allow association of the PCI address
with a "slot name" is encoding such information into the interface name really
necessary?
rick jones
WARNING: multiple messages have this Message-ID (diff)
From: Rick Jones <rick.jones2@hp.com>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: linux-hotplug@vger.kernel.org, netdev@vger.kernel.org,
narendra_k@dell.com, jcm@redhat.com, notting@redhat.com
Subject: Re: extended netdevice naming proposal
Date: Thu, 18 Nov 2010 10:34:29 -0800 [thread overview]
Message-ID: <4CE571B5.9070600@hp.com> (raw)
In-Reply-To: <20101117220659.GA12177@auslistsprd01.us.dell.com>
With the presence of the pci_slot driver to allow association of the PCI address
with a "slot name" is encoding such information into the interface name really
necessary?
rick jones
next prev parent reply other threads:[~2010-11-18 18:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 22:06 extended netdevice naming proposal Matt Domsch
2010-11-17 22:06 ` Matt Domsch
2010-11-18 0:39 ` Ben Hutchings
2010-11-18 2:10 ` Bill Nottingham
2010-11-18 2:10 ` Bill Nottingham
2010-11-18 2:29 ` Ben Hutchings
2010-11-18 18:51 ` Matt Domsch
2010-11-18 18:51 ` Matt Domsch
2010-11-18 19:00 ` Ben Hutchings
2010-11-18 18:34 ` Rick Jones [this message]
2010-11-18 18:34 ` Rick Jones
2010-11-18 18:52 ` Matt Domsch
2010-11-18 18:52 ` Matt Domsch
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=4CE571B5.9070600@hp.com \
--to=rick.jones2@hp.com \
--cc=Matt_Domsch@dell.com \
--cc=jcm@redhat.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=narendra_k@dell.com \
--cc=netdev@vger.kernel.org \
--cc=notting@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.