From: Greg KH <greg@kroah.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-arch@vger.kernel.org, Chris Zankel <chris@zankel.net>,
Grant Grundler <grundler@parisc-linux.org>,
linux-parisc@vger.kernel.org, Matthew Wilcox <matthew@wil.cx>,
Kyle McMartin <kyle@parisc-linux.org>,
linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
linux-pci@atrey.karlin.mff.cuni.cz,
linux-arm-kernel@lists.arm.linux.org.uk,
Russell King <rmk@arm.linux.org.uk>,
Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: [patch 01/16] PCI: add generic pci_enable_resources()
Date: Wed, 5 Mar 2008 12:14:26 -0800 [thread overview]
Message-ID: <20080305201426.GD13569@kroah.com> (raw)
In-Reply-To: <20894.1204728811@redhat.com>
On Wed, Mar 05, 2008 at 02:53:31PM +0000, David Howells wrote:
>
> Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
>
> > Each architecture has its own pcibios_enable_resources() implementation.
> > These differ in many minor ways that have nothing to do with actual
> > architectural differences. Follow-on patches will make most arches
> > use this generic version instead.
> >
> > This version is based on powerpc, which seemed most up-to-date. The only
> > functional difference from the x86 version is that this uses "!r->parent"
> > to check for resource collisions instead of "!r->start && r->end".
> >
> > Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
>
> Acked-by: David Howells <dhowells@redhat.com>
added, thanks.
greg k-h
next prev parent reply other threads:[~2008-03-05 20:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 18:56 [patch 00/16] PCI: consolidate several pcibios_enable_resources() implementations, v3 Bjorn Helgaas
2008-03-04 18:56 ` [patch 01/16] PCI: add generic pci_enable_resources() Bjorn Helgaas
2008-03-04 18:56 ` [patch 02/16] alpha: use " Bjorn Helgaas
2008-03-04 18:56 ` [patch 03/16] arm: " Bjorn Helgaas
2008-03-04 18:56 ` [patch 04/16] cris: " Bjorn Helgaas
2008-03-04 18:56 ` [patch 05/16] frv: " Bjorn Helgaas
2008-03-04 18:56 ` [patch 06/16] ia64: " Bjorn Helgaas
2008-03-04 18:56 ` [patch 07/16] mips: " Bjorn Helgaas
2008-03-04 18:56 ` [patch 08/16] mn10300: " Bjorn Helgaas
2008-03-04 18:56 ` [patch 09/16] parisc: " Bjorn Helgaas
2008-03-05 16:17 ` Kyle McMartin
2008-03-05 20:09 ` Greg KH
2008-03-04 18:56 ` [patch 10/16] powerpc: " Bjorn Helgaas
2008-03-04 18:56 ` [patch 11/16] ppc: " Bjorn Helgaas
2008-03-04 18:56 ` [patch 12/16] sh: " Bjorn Helgaas
2008-03-04 18:56 ` [patch 13/16] sparc64: " Bjorn Helgaas
2008-03-04 18:57 ` [patch 14/16] v850: " Bjorn Helgaas
2008-03-04 18:57 ` [patch 15/16] x86: " Bjorn Helgaas
2008-03-04 18:57 ` [patch 16/16] xtensa: " Bjorn Helgaas
2008-03-05 14:52 ` [patch 05/16] frv: " David Howells
2008-03-05 20:14 ` Greg KH
2008-03-05 14:53 ` [patch 01/16] PCI: add " David Howells
2008-03-05 20:14 ` Greg KH [this message]
2008-03-05 15:13 ` [patch 08/16] mn10300: use " David Howells
2008-03-05 20:15 ` 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=20080305201426.GD13569@kroah.com \
--to=greg@kroah.com \
--cc=bjorn.helgaas@hp.com \
--cc=chris@zankel.net \
--cc=dhowells@redhat.com \
--cc=grundler@parisc-linux.org \
--cc=kyle@parisc-linux.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linuxppc-dev@ozlabs.org \
--cc=matthew@wil.cx \
--cc=paulus@samba.org \
--cc=rmk@arm.linux.org.uk \
/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).