From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] sysfs: add per pci device msi[x] irq listing (v4)
Date: Fri, 30 Sep 2011 14:32:11 +0200 [thread overview]
Message-ID: <20110930143211.5ab39c02@stein> (raw)
In-Reply-To: <1317307129-11579-1-git-send-email-nhorman@tuxdriver.com>
On Sep 29 Neil Horman wrote:
> (v4)
> Fixed up some spelling mistakes, and added a scissors line with a good
> commitlog, so that git-am drops all the version logging
>
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
> CC: Greg Kroah-Hartman <gregkh@suse.de>
> CC: Jesse Barnes <jbarnes@virtuousgeek.org>
> CC: Bjorn Helgaas <bhelgaas@google.com>
> CC: linux-pci@vger.kernel.org
It drops these last 5 lines then too, doesn't it?
> --- a/Documentation/ABI/testing/sysfs-bus-pci
> +++ b/Documentation/ABI/testing/sysfs-bus-pci
> @@ -66,6 +66,24 @@ Description:
> re-discover previously removed devices.
> Depends on CONFIG_HOTPLUG.
>
> +What: /sys/bus/pci/devices/.../msi_irqs/
> +Date: September, 2011
> +Contact: Neil Horman <nhorman@tuxdriver.com>
> +Description:
> + The /sys/devices/.../msi_irqs directory contains a variable set
> + sub-directories, with each sub-directory being named after a
> + corresponding msi irq vector allocated to that device.
"contains a variable set _of_ sub-directories"?
--
Stefan Richter
-=====-==-== =--= ====-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2011-09-30 12:32 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 18:36 [PATCH] sysfs: add per pci device msi[x] irq listing Neil Horman
2011-09-15 14:40 ` Greg KH
2011-09-15 15:07 ` Neil Horman
2011-09-15 20:08 ` [PATCH] sysfs: add per pci device msi[x] irq listing (v2) Neil Horman
2011-09-16 8:36 ` Greg KH
2011-09-16 10:57 ` Neil Horman
2011-09-16 13:23 ` Greg KH
2011-09-16 13:32 ` Neil Horman
2011-09-16 16:12 ` Bjorn Helgaas
2011-09-19 15:47 ` [PATCH] sysfs: add per pci device msi[x] irq listing (v3) Neil Horman
2011-09-19 17:14 ` Greg KH
2011-09-19 17:33 ` Neil Horman
2011-09-22 10:49 ` Konrad Rzeszutek Wilk
2011-09-22 10:57 ` Neil Horman
2011-09-22 11:10 ` Konrad Rzeszutek Wilk
2011-09-22 13:21 ` Neil Horman
2011-09-22 13:17 ` Neil Horman
2011-09-22 13:54 ` Matthew Wilcox
2011-09-22 14:32 ` Neil Horman
2011-09-28 22:18 ` Bjorn Helgaas
2011-09-29 0:42 ` Neil Horman
2011-09-29 4:40 ` Bjorn Helgaas
2011-09-29 13:07 ` Neil Horman
2011-09-29 14:38 ` [PATCH] sysfs: add per pci device msi[x] irq listing (v4) Neil Horman
2011-09-29 14:51 ` Greg KH
2011-09-30 12:32 ` Stefan Richter [this message]
2011-09-30 15:33 ` Neil Horman
2011-09-30 16:33 ` Bjorn Helgaas
2011-09-30 16:54 ` Neil Horman
2011-10-06 15:36 ` Jesse Barnes
2011-10-06 17:12 ` Neil Horman
2011-10-06 17:57 ` Bjorn Helgaas
2011-10-06 18:08 ` [PATCH] sysfs: add per pci device msi[x] irq listing (v5) Neil Horman
2011-10-14 16:21 ` Jesse Barnes
2011-10-14 16:40 ` Greg KH
2011-10-14 17:31 ` Neil Horman
2011-11-01 16:47 ` Neil Horman
2011-11-01 16:58 ` Jesse Barnes
2011-11-01 18:05 ` Neil Horman
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=20110930143211.5ab39c02@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=bhelgaas@google.com \
--cc=gregkh@suse.de \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nhorman@tuxdriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox