From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Bjorn Helgaas <bhelgaas@google.com>,
Richard Henderson <rth@twiddle.net>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
David Howells <dhowells@redhat.com>,
Russell King <linux@arm.linux.org.uk>,
Tony Luck <tony.luck@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Ingo Molnar <mingo@redhat.com>,
Guenter Roeck <linux@roeck-us.net>,
Michal Simek <monstr@monstr.eu>, Chris Zankel <chris@zankel.net>,
Arnd Bergmann <arnd@arndb.de>, Krzysztof Halasa <khalasa@piap.pl>,
Phil Edworthy <phil.edworthy@renesas.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Jingoo Han <jg1.han@samsung.com>,
Lucas Stach <l.stach@pengutronix.de>,
Simon Horman <horms@verge.net.au>,
Minghuan Lian <minghuan.Lian@freescale.com>,
Murali Karicheri <m-karicheri2@ti.com>,
Tanmay Inamdar <tinamdar@apm.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Thierry Reding <thierry.reding@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Will Deacon <Will.Deacon@arm.com>,
Jayachandran C <jchandra@broadcom.com>
Subject: Re: [RFC/RFT PATCH v2] PCI: move pci_read_bridge_bases to the generic PCI layer
Date: Tue, 16 Jun 2015 10:55:07 +0100 [thread overview]
Message-ID: <20150616095507.GB24710@red-moon> (raw)
In-Reply-To: <5579E74A.3000808@amd.com>
On Thu, Jun 11, 2015 at 08:53:46PM +0100, Suravee Suthikulanit wrote:
> For ARM64 PROBE_ONLY and non-PROBE_ONLY modes:
>
> Reviewed and Tested-by: Suravee Suthikulpanit
> <Suravee.Suthikulpanit@amd.com>
Thank you !
> Please see minor comments below.
[...]
> > +static void pci_claim_bridge_resources(struct pci_bus *bus)
> > +{
> > + struct pci_dev *dev = bus->self;
> > + int idx;
> > +
> > + for (idx = PCI_BRIDGE_RESOURCES; idx < PCI_NUM_RESOURCES; idx++) {
> > + struct resource *r = &dev->resource[idx];
> > +
> > + if (!r->flags || r->parent)
> > + continue;
> > +
> > + pci_claim_bridge_resource(dev, idx);
> > + }
> > +}
> > +
>
> Nitpicking: Since pci_claim_bridge_resources() is small, and only called
> once from pci_read_brdige_bases(), should we just put the loop inside
> the function?
I think it is ok to add a function for it, I am not fussed either
way I am more concerned by testing the patch on archs I do not have
access to.
Thank you,
Lorenzo
next prev parent reply other threads:[~2015-06-16 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 9:01 [RFC/RFT PATCH v2] PCI: move pci_read_bridge_bases to the generic PCI layer Lorenzo Pieralisi
2015-06-11 19:53 ` Suravee Suthikulanit
2015-06-16 9:55 ` Lorenzo Pieralisi [this message]
2015-06-12 8:04 ` Guenter Roeck
2015-06-13 1:47 ` Guenter Roeck
2015-06-13 9:12 ` Lorenzo Pieralisi
2015-06-14 15:29 ` Guenter Roeck
2015-06-15 10:31 ` Lorenzo Pieralisi
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=20150616095507.GB24710@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=Will.Deacon@arm.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=chris@zankel.net \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=horms@verge.net.au \
--cc=jchandra@broadcom.com \
--cc=jejb@parisc-linux.org \
--cc=jg1.han@samsung.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=khalasa@piap.pl \
--cc=kishon@ti.com \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@roeck-us.net \
--cc=m-karicheri2@ti.com \
--cc=minghuan.Lian@freescale.com \
--cc=mingo@redhat.com \
--cc=monstr@monstr.eu \
--cc=mpe@ellerman.id.au \
--cc=phil.edworthy@renesas.com \
--cc=ralf@linux-mips.org \
--cc=rth@twiddle.net \
--cc=suravee.suthikulpanit@amd.com \
--cc=thierry.reding@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tinamdar@apm.com \
--cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).