On Thu, Feb 21, 2013 at 4:47 PM, Andrew Murray <Andrew.Murray@xxxxxxx> wrote: > DT bindings for PCI host bridges often use the ranges property to describe > memory and IO ranges - this binding tends to be the same across architectures > yet several parsing implementations exist, e.g. arch/mips/pci/pci.c, > arch/powerpc/kernel/pci-common.c, arch/sparc/kernel/pci.c and > arch/microblaze/pci/pci-common.c (clone of PPC). Some of these duplicate > functionality provided by drivers/of/address.c. Hm I wanted to test but was blocked by this: Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Making the raw patch look like this: =09const u32 *ranges; -=09int rlen; -=09int pna =3D of_n_addr_cells(dev); -=09int np =3D pna + 5; =09int memno =3D 0, isa_hole =3D -1; I bet the other ARM guys can help you get the format right somehow... can't you just use git send-email? Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
