From: Len Brown <lenb@kernel.org>
To: Dan Williams <dcbw@redhat.com>
Cc: Matt Domsch <Matt_Domsch@dell.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-hotplug@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Network Device Naming mechanism and policy
Date: Fri, 27 Mar 2009 16:06:44 +0000 [thread overview]
Message-ID: <alpine.LFD.2.00.0903271203140.26419@localhost.localdomain> (raw)
In-Reply-To: <1238098611.3254.8.camel@localhost.localdomain>
> > > So, please, put mapping tables into the ACPI or similar
ACPI added _PLD (Physical Device Location) back in 3.0, ISTR.
However, searching my archives, I have yet to see a single instance
of its use in the field.
ACPI also supplies the slot number stuff, which is exported via
the existing pci_slot driver.
cheers,
Len Brown, Intel Open Source Technology Center
WARNING: multiple messages have this Message-ID (diff)
From: Len Brown <lenb@kernel.org>
To: Dan Williams <dcbw@redhat.com>
Cc: Matt Domsch <Matt_Domsch@dell.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-hotplug@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Network Device Naming mechanism and policy
Date: Fri, 27 Mar 2009 12:06:44 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0903271203140.26419@localhost.localdomain> (raw)
In-Reply-To: <1238098611.3254.8.camel@localhost.localdomain>
> > > So, please, put mapping tables into the ACPI or similar
ACPI added _PLD (Physical Device Location) back in 3.0, ISTR.
However, searching my archives, I have yet to see a single instance
of its use in the field.
ACPI also supplies the slot number stuff, which is exported via
the existing pci_slot driver.
cheers,
Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-03-27 16:06 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 15:46 Network Device Naming mechanism and policy Matt Domsch
2009-03-24 15:46 ` Matt Domsch
2009-03-24 16:21 ` Patrick McHardy
2009-03-24 16:21 ` Patrick McHardy
2009-03-24 16:28 ` Kay Sievers
2009-03-24 16:28 ` Kay Sievers
2009-03-24 16:38 ` Patrick McHardy
2009-03-24 16:38 ` Patrick McHardy
2009-03-24 16:40 ` Dan Williams
2009-03-24 16:40 ` Dan Williams
2009-03-24 17:00 ` Alan Cox
2009-03-24 17:04 ` Patrick McHardy
2009-03-24 17:04 ` Patrick McHardy
2009-03-24 18:51 ` david
2009-03-24 18:51 ` david
2009-03-24 21:02 ` Alan Cox
2009-03-24 23:14 ` Greg KH
2009-03-24 23:14 ` Greg KH
2009-03-24 16:42 ` Karl O. Pinc
2009-03-24 16:42 ` Karl O. Pinc
2009-03-24 17:45 ` Matt Domsch
2009-03-24 17:45 ` Matt Domsch
2009-03-24 17:02 ` Scott James Remnant
2009-03-24 17:52 ` Matt Domsch
2009-03-24 17:52 ` Matt Domsch
2009-03-24 18:12 ` Bill Nottingham
2009-03-24 18:12 ` Bill Nottingham
2009-03-24 18:20 ` Scott James Remnant
2009-03-24 18:49 ` david
2009-03-24 18:49 ` david
2009-03-24 19:22 ` Matt Domsch
2009-03-24 19:22 ` Matt Domsch
2009-03-24 22:57 ` David Miller
2009-03-24 22:57 ` David Miller
2009-03-25 20:22 ` Chris Friesen
2009-03-25 20:22 ` Chris Friesen
2009-03-26 20:17 ` Dan Williams
2009-03-26 20:17 ` Dan Williams
2009-03-26 16:39 ` Matt Domsch
2009-03-26 16:39 ` Matt Domsch
2009-03-26 20:16 ` Dan Williams
2009-03-26 20:16 ` Dan Williams
2009-03-27 16:06 ` Len Brown [this message]
2009-03-27 16:06 ` Len Brown
2009-04-09 14:58 ` Matt Domsch
2009-04-09 14:58 ` Matt Domsch
2009-03-31 14:07 ` Kurt Van Dijck
2009-03-31 14:07 ` Kurt Van Dijck
-- strict thread matches above, loose matches on Subject: below --
2009-08-05 19:50 Jordan_Hargrave
2009-08-05 21:49 ` Alan Jenkins
2009-08-06 8:15 ` Alan Jenkins
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=alpine.LFD.2.00.0903271203140.26419@localhost.localdomain \
--to=lenb@kernel.org \
--cc=Matt_Domsch@dell.com \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=linux-hotplug@vger.kernel.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 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.