From: Greg KH <greg@kroah.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 V3] Export SMBIOS provided firmware instance and label
Date: Fri, 23 Jul 2010 13:55:57 +0000 [thread overview]
Message-ID: <20100723135557.GA3624@kroah.com> (raw)
In-Reply-To: <20100723133456.GA9378@auslistsprd01.us.dell.com>
On Fri, Jul 23, 2010 at 08:34:56AM -0500, Narendra K wrote:
> --- a/Documentation/ABI/testing/sysfs-bus-pci
> +++ b/Documentation/ABI/testing/sysfs-bus-pci
> @@ -179,3 +179,30 @@ Contact: linux-pci@vger.kernel.org
> Description:
> This symbolic link points to the PCI hotplug controller driver
> module that manages the hotplug slot.
> +
> +What: /sys/bus/pci/devices/.../label
> +Date: July 2010
> +Contact: linux-bugs@dell.com
that's not your email address. Please don't hide behind some random
address, Linux is about contacting developers directly were ever
possible.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.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 V3] Export SMBIOS provided firmware instance and label to sysfs
Date: Fri, 23 Jul 2010 06:55:57 -0700 [thread overview]
Message-ID: <20100723135557.GA3624@kroah.com> (raw)
In-Reply-To: <20100723133456.GA9378@auslistsprd01.us.dell.com>
On Fri, Jul 23, 2010 at 08:34:56AM -0500, Narendra K wrote:
> --- a/Documentation/ABI/testing/sysfs-bus-pci
> +++ b/Documentation/ABI/testing/sysfs-bus-pci
> @@ -179,3 +179,30 @@ Contact: linux-pci@vger.kernel.org
> Description:
> This symbolic link points to the PCI hotplug controller driver
> module that manages the hotplug slot.
> +
> +What: /sys/bus/pci/devices/.../label
> +Date: July 2010
> +Contact: linux-bugs@dell.com
that's not your email address. Please don't hide behind some random
address, Linux is about contacting developers directly were ever
possible.
thanks,
greg k-h
next prev parent reply other threads:[~2010-07-23 13:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EDA0A4495861324DA2618B4C45DCB3EE612C40@blrx3m08.blr.amer.dell.com>
2010-07-23 13:34 ` [PATCH V3] Export SMBIOS provided firmware instance and label to sysfs Narendra K
2010-07-23 13:34 ` Narendra K
2010-07-23 13:55 ` Greg KH [this message]
2010-07-23 13:55 ` Greg KH
2010-07-23 14:58 ` Matt Domsch
2010-07-23 14:58 ` Matt Domsch
2010-07-26 18:20 ` [PATCH V3] Export SMBIOS provided firmware instance and label Greg KH
2010-07-26 18:20 ` [PATCH V3] Export SMBIOS provided firmware instance and label to sysfs Greg KH
2010-07-22 18:44 Narendra K
2010-07-22 18:56 ` [PATCH V3] Export SMBIOS provided firmware instance and label Greg KH
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=20100723135557.GA3624@kroah.com \
--to=greg@kroah.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 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.