netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Narendra_K@Dell.com>
To: <greg@kroah.com>
Cc: <kay.sievers@vrfy.org>, <Matt_Domsch@Dell.com>,
	<netdev@vger.kernel.org>, <linux-hotplug@vger.kernel.org>,
	<linux-pci@vger.kernel.org>, <Jordan_Hargrave@Dell.com>,
	<Vijay_Nijhawan@Dell.com>, <Charles_Rose@Dell.com>
Subject: Re: [PATCH V2] Use firmware provided index to register a network interface
Date: Thu, 7 Oct 2010 23:14:46 +0530	[thread overview]
Message-ID: <20101007174435.GA2939@libnet-test.oslab.blr.amer.dell.com> (raw)
In-Reply-To: <20101007171532.GA29857@kroah.com>

On Thu, Oct 07, 2010 at 10:45:32PM +0530, Greg KH wrote:
>    On Thu, Oct 07, 2010 at 07:05:14PM +0200, Kay Sievers wrote:
>    > On Thu, Oct 7, 2010 at 18:48, Greg KH <greg@kroah.com> wrote:
>    > > On Thu, Oct 07, 2010 at 11:31:13AM -0500, Matt Domsch wrote:
>    > >> 1) SMBIOS type 41 method.  Windows does not use this today, and I
>    > >>    can't speak to their future plans.  Narendra's kernel patch does,
>    > >>    as has biosdevname, the udev helper we first wrote for this
>    > >>    purpose, for several years.
>    > >
>    > > Then stick with that udev helper please :)
>    >
>    > What about just exporting this information in sysfs, and not touch the
>    naming?
> 
>    I think this is now exported in userspace, right Narendra?
> 

Right. It is in the mainline kernel.
( commit 911e1c9b05a8e3559a7aa89083930700a0b9e7ee)

-- 
With regards,
Narendra K

  reply	other threads:[~2010-10-07 17:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07 14:23 [PATCH V2] Use firmware provided index to register a network interface Narendra_K
2010-10-07 15:11 ` Greg KH
2010-10-07 16:31   ` Matt Domsch
2010-10-07 16:48     ` Greg KH
2010-10-07 17:05       ` Kay Sievers
2010-10-07 17:15         ` Greg KH
2010-10-07 17:44           ` Narendra_K [this message]
2010-10-07 18:44         ` Narendra_K
2010-10-07 20:42         ` Matt Domsch
2010-10-07 16:49     ` David Lamparter
2010-10-07 17:13       ` Kay Sievers
2010-10-07 16:14 ` 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=20101007174435.GA2939@libnet-test.oslab.blr.amer.dell.com \
    --to=narendra_k@dell.com \
    --cc=Charles_Rose@Dell.com \
    --cc=Jordan_Hargrave@Dell.com \
    --cc=Matt_Domsch@Dell.com \
    --cc=Vijay_Nijhawan@Dell.com \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-hotplug@vger.kernel.org \
    --cc=linux-pci@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).