[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <EDA0A4495861324DA2618B4C45DCB3EE61285B@blrx3m08.blr.amer.dell.com>
Date: Mon, 31 May 2010 13:25:34 +0530
From: <Narendra_K@...l.com>
To: <Matt_Domsch@...l.com>, <greg@...ah.com>
Cc: <netdev@...r.kernel.org>, <linux-hotplug@...r.kernel.org>,
<linux-pci@...r.kernel.org>, <Jordan_Hargrave@...l.com>,
<Charles_Rose@...l.com>, <Vijay_Nijhawan@...l.com>
Subject: RE: [PATCH 1/2] Export firmware assigned labels of network devices to sysfs
> -----Original Message-----
> From: Matt Domsch [mailto:Matt_Domsch@...l.com]
> Sent: Friday, May 28, 2010 11:41 PM
> To: Greg KH
> Cc: K, Narendra; netdev@...r.kernel.org;
linux-hotplug@...r.kernel.org;
> linux-pci@...r.kernel.org; Hargrave, Jordan; Rose, Charles; Nijhawan,
> Vijay
> Subject: Re: [PATCH 1/2] Export firmware assigned labels of network
> devices to sysfs
>
> On Fri, May 28, 2010 at 08:40:41AM -0700, Greg KH wrote:
> > On Fri, May 28, 2010 at 06:55:21AM -0500, K, Narendra wrote:
> > > +static const char dell_dsm_uuid[] = {
> >
> > Um, a dell specific uuid in a generic file? What happens when we
> need
> > to support another manufacturer?
> >
> > > + 0xD0, 0x37, 0xC9, 0xE5, 0x53, 0x35, 0x7A, 0x4D,
> > > + 0x91, 0x17, 0xEA, 0x4D, 0x19, 0xC3, 0x43, 0x4D
> > > +};
>
> This simply needs to be renamed. It's defined in the ECN, so will be
> part of the spec, and is not vendor-unique, but defined once for all
> implementations. It separates this _DSM function from others.
>
> Thanks for the quick feedback.
Matt,
Thanks for the clarification. My understanding of the uuid was
incorrect. Would address this in the next version of the patch.
With regards,
Narendra K
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists