From: Tim Small <tim@buttersideup.com>
To: Narendra K <Narendra_K@dell.com>
Cc: netdev@vger.kernel.org, linux-hotplug@vger.kernel.org,
linux-pci@vger.kernel.org, matt_domsch@dell.com,
charles_rose@dell.com, jordan_hargrave@dell.com,
vijay_nijhawan@dell.com
Subject: Re: [PATCH] Use firmware provided index to register a network interface
Date: Wed, 22 Sep 2010 22:07:53 +0000 [thread overview]
Message-ID: <4C9A7E39.2020304@buttersideup.com> (raw)
In-Reply-To: <20100922183137.GA7607@auslistsprd01.us.dell.com>
Narendra K wrote:
> Hello,
>
> Here is another approach to address the issue of "eth0 does not always
> map to the Integrated NIC Port 1 as denoted on server chassis label".
> For more details please refer to the thread -
> http://marc.info/?l=linux-netdev&m\x128163454631618&w=3.
>
Hi,
Out of interest, that link says that doing it in usespace was rejected,
but doesn't give any references... I'd be interested to know why this
wasn't viable - since this seemed like the best fit at first glance -
most people will never use this, so no need to grow their kernel size
and complexity?
Cheers,
Tim.
next prev parent reply other threads:[~2010-09-22 22:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 18:31 [PATCH] Use firmware provided index to register a network interface Narendra K
2010-09-22 19:22 ` [PATCH] Use firmware provided index to register a network Greg KH
2010-09-23 15:22 ` [PATCH] Use firmware provided index to register a network interface Narendra_K
2010-09-23 15:27 ` [PATCH] Use firmware provided index to register a network Greg KH
2010-09-23 15:51 ` [PATCH] Use firmware provided index to register a network interface Narendra_K
2010-09-23 16:33 ` [PATCH] Use firmware provided index to register a network Greg KH
2010-10-07 14:26 ` Narendra_K
2010-10-07 14:27 ` [PATCH] Use firmware provided index to register a network interface Tim Small
2010-10-07 14:31 ` [PATCH] Use firmware provided index to register a network Greg KH
2010-09-22 22:07 ` Tim Small [this message]
2010-09-22 22:16 ` Stephen Hemminger
2010-09-23 6:34 ` [PATCH] Use firmware provided index to register a network interface Tim Small
2010-09-23 15:25 ` Narendra_K
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=4C9A7E39.2020304@buttersideup.com \
--to=tim@buttersideup.com \
--cc=Narendra_K@dell.com \
--cc=charles_rose@dell.com \
--cc=jordan_hargrave@dell.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matt_domsch@dell.com \
--cc=netdev@vger.kernel.org \
--cc=vijay_nijhawan@dell.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 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).