From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Matt Domsch <Matt_Domsch@Dell.com>
Cc: Narendra_K@Dell.com, linux-pci@vger.kernel.org,
linux-hotplug@vger.kernel.org, netdev@vger.kernel.org,
Jordan_Hargrave@Dell.com, Charles_Rose@Dell.com,
Vijay_Nijhawan@Dell.com
Subject: Re: [PATCH] Export ACPI _DSM provided firmware instance number and string name to sysfs
Date: Wed, 5 Jan 2011 14:46:15 -0800 [thread overview]
Message-ID: <20110105144615.3d4090ea@jbarnes-desktop> (raw)
In-Reply-To: <20110105224404.GB4647@auslistsprd01.us.dell.com>
On Wed, 5 Jan 2011 16:44:04 -0600
Matt Domsch <Matt_Domsch@Dell.com> wrote:
> On Thu, Dec 23, 2010 at 11:24:36AM -0800, Narendra_K@Dell.com wrote:
> > Please find the version 2 of the patch.
> >
> > V1 -> V2:
> >
> > The attribute 'index' is changed to 'acpi_index' as the semantics of
> > SMBIOS provided device type instance and ACPI _DSM provided instance
> > number are different.
> >
> > From: Narendra K <narendra_k@dell.com>
> > Subject: [PATCH V2] Export ACPI _DSM provided firmware instance number and string to sysfs
> >
> > This patch exports ACPI _DSM (Device Specific Method) provided firmware
> > instance number and string name of PCI devices as defined by
> > 'PCI Firmware Specification Revision 3.1' section 4.6.7.( DSM for Naming
> > a PCI or PCI Express Device Under Operating Systems) to sysfs.
>
> Thanks Narendra and Jordan.
>
> Jesse, how does this look for -next please?
I think it's fine; I'll check it out again and apply this week.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-01-05 22:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 16:42 [PATCH] Export ACPI _DSM provided firmware instance number and string name to sysfs Narendra_K
2010-12-23 14:32 ` Matt Domsch
2010-12-23 19:24 ` Narendra_K
2011-01-05 22:44 ` Matt Domsch
2011-01-05 22:46 ` Jesse Barnes [this message]
2011-01-07 22:27 ` Jesse Barnes
2011-01-10 18:48 ` Narendra_K
2011-01-10 19:13 ` Jesse Barnes
2011-01-10 19:35 ` 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=20110105144615.3d4090ea@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=Charles_Rose@Dell.com \
--cc=Jordan_Hargrave@Dell.com \
--cc=Matt_Domsch@Dell.com \
--cc=Narendra_K@Dell.com \
--cc=Vijay_Nijhawan@Dell.com \
--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).