From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/3] of/pci: Unify pci_process_bridge_OF_ranges from Microblaze and PowerPC
Date: Thu, 11 Apr 2013 17:28:54 +0200 [thread overview]
Message-ID: <20130411172854.61f5728e@skate> (raw)
In-Reply-To: <20130411121242.GB28981@arm.com>
Dear Andrew Murray,
On Thu, 11 Apr 2013 13:12:42 +0100, Andrew Murray wrote:
> Thanks - I somehow missed this.
>
> I've included this change in my next respin - but I've put
> 'struct pci_controller' immediately before
> 'pci_process_bridge_OF_ranges' rather than above of_irq_map_pci to be
> consistent with the rest of the file.
Right, sounds good.
Do we have some news from the PowerPC and Microblaze maintainers about
their acceptance of PATCH 1/3 ? This of/pci thing is the only last
remaining patch for which I need a Ack to get the Marvell PCIe merged.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-04-11 15:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 7:29 [PATCH v5 0/3] of/pci: Provide common support for PCI DT parsing Andrew Murray
2013-04-10 7:29 ` [PATCH v5 1/3] of/pci: Unify pci_process_bridge_OF_ranges from Microblaze and PowerPC Andrew Murray
2013-04-10 13:13 ` Rob Herring
2013-04-10 21:30 ` Thomas Petazzoni
2013-04-11 16:57 ` Linus Walleij
2013-04-11 12:03 ` Andrew Murray
2013-04-10 21:33 ` Thomas Petazzoni
2013-04-11 12:12 ` Andrew Murray
2013-04-11 15:28 ` Thomas Petazzoni [this message]
2013-04-10 7:29 ` [PATCH v5 2/3] of/pci: Provide support for parsing PCI DT ranges property Andrew Murray
2013-04-10 18:26 ` Rob Herring
2013-04-11 13:11 ` Andrew Murray
2013-04-10 7:29 ` [PATCH v5 3/3] of/pci: mips: convert to common of_pci_range_parser Andrew Murray
2013-04-10 18:28 ` Rob Herring
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=20130411172854.61f5728e@skate \
--to=thomas.petazzoni@free-electrons.com \
--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;
as well as URLs for NNTP newsgroup(s).