From: John Crispin <blogic@openwrt.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: [PATCH 02/14] MIPS: pci: parse memory ranges from devicetree
Date: Thu, 03 May 2012 21:39:32 +0200 [thread overview]
Message-ID: <4FA2DEF4.9050506@openwrt.org> (raw)
In-Reply-To: <CAMuHMdWkd4YYKp1dBOFXyLFUT=Jc0iE3nb5OqbT6isQ977z1_w@mail.gmail.com>
Hi Geert,
> There's no pci_load_of_ranges() in arch/powerpc/?
>
Sorry, its based on pci_process_bridge_OF_ranges.
I will fold your comments into the patch,
Thanks,
John
next prev parent reply other threads:[~2012-05-03 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 17:42 [PATCH 02/14] MIPS: pci: parse memory ranges from devicetree John Crispin
2012-05-03 19:30 ` Geert Uytterhoeven
2012-05-03 19:39 ` John Crispin [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-30 11:32 [PATCH 01/14] MIPS: make oprofile use cp0_perfcount_irq if it is set John Crispin
2012-04-30 11:32 ` [PATCH 02/14] MIPS: pci: parse memory ranges from devicetree John Crispin
2012-04-30 16:55 ` David Daney
2012-04-30 17:02 ` John Crispin
2012-05-01 11:17 ` John Crispin
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=4FA2DEF4.9050506@openwrt.org \
--to=blogic@openwrt.org \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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