From: benh@kernel.crashing.org (Benjamin Herrenschmidt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 1/3] of/pci: Unify pci_process_bridge_OF_ranges from Microblaze and PowerPC
Date: Tue, 07 May 2013 20:19:18 +1000 [thread overview]
Message-ID: <1367921958.25488.8.camel@pasglop> (raw)
In-Reply-To: <20130507080142.GA8808@arm.com>
On Tue, 2013-05-07 at 09:01 +0100, Andrew Murray wrote:
>
> There were no objections to this latest revision until now and it is
> currently sitting with Jason Cooper (mvebu-next/pcie). [1]
Ok, well I've just sent Linus a pull request for my changes so at least
drop the powerpc changes from your tree for the time being.
> This is a view that was also shared by Bjorn [2] when I attempted to
> submit a patchset which moves struct pci_controller to asm-generic.
Right, it's the logical way to go
> The motativation for my patchsets were to give a way for ARM PCI host
> bridge drivers to parse the DT ranges property, but this snow-balled
> into unifying pci_process_bridge_OF_ranges.
Which I understand, I would probably have done the same thing in your
shoes :-)
> My v8 patchset provides a of_pci_range_parser which is used directly
> by a few ARM PCI DT host bridge drivers, this has been generally
> accepted and tested. I don't see why this can't remain and so I'd
> really like to keep this around.
Sure, no objection, in fact I should/could probably update my new code
to use it as well.
> Grant, Benjamin would you be happy for me to resubmit this series
> which provides the of_pci_range_parser which will be used by the
> separate implementations of pci_process_bridge_OF_ranges in
> PowerPC/Microblaze?
Sure, in fact feel free to update my new code if you have more bandwidth
than I do, it should hit Linus tree soon hopefully unless he objects to
me having a second pull request this merge window...
> Benjamin are you able to still use of_pci_range_parser in your
> 'Support per-aperture memory offset' patch?
I see no reason why not. I just haven't looked into it much, I admit,
being bogged down with a pile of new HW bringup in the lab etc...
Cheers,
Ben.
next prev parent reply other threads:[~2013-05-07 10:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 10:41 [PATCH v8 0/3] of/pci: Provide common support for PCI DT parsing Andrew Murray
2013-04-22 10:41 ` [PATCH v8 1/3] of/pci: Unify pci_process_bridge_OF_ranges from Microblaze and PowerPC Andrew Murray
2013-05-05 2:41 ` Benjamin Herrenschmidt
2013-05-07 8:01 ` Andrew Murray
2013-05-07 10:19 ` Benjamin Herrenschmidt [this message]
2013-04-22 10:41 ` [PATCH v8 2/3] of/pci: Provide support for parsing PCI DT ranges property Andrew Murray
2013-04-26 9:33 ` 한진구
2013-04-22 10:41 ` [PATCH v8 3/3] of/pci: mips: convert to common of_pci_range_parser Andrew Murray
2013-04-22 16:53 ` [PATCH v8 0/3] of/pci: Provide common support for PCI DT parsing Jason Cooper
2013-04-22 23:02 ` Jason Cooper
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=1367921958.25488.8.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux-arm-kernel@lists.infradead.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