From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: linux-pci@atrey.karlin.mff.cuni.cz, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org, willy@debian.org
Subject: Re: [PATCH] add legacy I/O port & memory APIs to /proc/bus/pci
Date: Thu, 16 Dec 2004 08:39:20 -0800 [thread overview]
Message-ID: <41C1BA38.60304@osdl.org> (raw)
In-Reply-To: <200412160850.20223.jbarnes@engr.sgi.com>
Jesse Barnes wrote:
> This patch documents the /proc/bus/pci interface and adds some optional
> architecture specific APIs for accessing legacy I/O port and memory space.
> This is necessary on platforms where legacy I/O port space doesn't 'soft
> fail' like it does on PCs, and is useful for systems that can route legacy
> space to different PCI busses.
>
> I've incorporated all the feedback I've received so far, so I think it's ready
> to send on to Andrew for inclusion, if someone could give the proc-pci.txt
> documentation a last read (and/or comment on other stuff I may have missed).
meta-comment:
Would you (and not just you :) include a diffstat summary so we
can see which files are being changed? something like this:
Documentation/filesystems/proc-pci.txt | 126
+++++++++++++++++++++++++++++++++
arch/ia64/pci/pci.c | 105
+++++++++++++++++++++++++++
arch/ia64/sn/pci/pci_dma.c | 74 +++++++++++++++++++
drivers/pci/proc.c | 100 +++++++++++++++++++++++---
include/asm-ia64/machvec.h | 24 ++++++
include/asm-ia64/machvec_init.h | 3
include/asm-ia64/machvec_sn2.h | 6 +
include/asm-ia64/pci.h | 4 +
include/asm-ia64/sn/sn_sal.h | 47 ++++++++++++
include/linux/pci.h | 12 ++-
10 files changed, 488 insertions(+), 13 deletions(-)
--
~Randy
next prev parent reply other threads:[~2004-12-16 17:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 16:50 [PATCH] add legacy I/O port & memory APIs to /proc/bus/pci Jesse Barnes
2004-12-16 16:39 ` Randy.Dunlap [this message]
2004-12-16 17:07 ` Jesse Barnes
2004-12-16 17:55 ` Doug Maxey
2004-12-16 16:56 ` Christoph Hellwig
2004-12-16 17:04 ` Jesse Barnes
2004-12-16 17:37 ` Bjorn Helgaas
2004-12-16 17:42 ` Jesse Barnes
2004-12-16 18:45 ` David Mosberger
2004-12-16 18:56 ` Jesse Barnes
2004-12-16 19:07 ` Jesse Barnes
2004-12-16 19:11 ` David Mosberger
2004-12-16 19:13 ` Jesse Barnes
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=41C1BA38.60304@osdl.org \
--to=rddunlap@osdl.org \
--cc=jbarnes@engr.sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=willy@debian.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