diff for duplicates of <4FD7B085.1020006@firmworks.com> diff --git a/a/1.txt b/N1/1.txt index a1527bf..119af8d 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -26,12 +26,12 @@ On 6/12/2012 10:15 AM, Stephen Warren wrote: >> #address-cells =<1>; >> #size-cells =<1>; >> ->> port@80000000 { +>> port at 80000000 { >> reg =<0x80000000 0x00001000>; >> status = "disabled"; >> }; >> ->> port@80001000 { +>> port at 80001000 { >> reg =<0x80001000 0x00001000>; >> status = "disabled"; >> }; @@ -46,7 +46,7 @@ On 6/12/2012 10:15 AM, Stephen Warren wrote: > > As a general concept, this kind of design seems OK to me. > -> The "port" child nodes I think should be named "pci@..." given Mitch's +> The "port" child nodes I think should be named "pci at ..." given Mitch's > comments, I think. > > The port nodes probably need two entries in reg, given the following in @@ -75,12 +75,12 @@ On 6/12/2012 10:15 AM, Stephen Warren wrote: > PCIe controller's register space based on the ID using code roughly like > what I quoted above: > -> pci@0 { +> pci at 0 { > reg =<0>; > status = "disabled"; > }; > -> pci@1 { +> pci at 1 { > reg =<0>; > status = "disabled"; > }; @@ -111,6 +111,6 @@ calculation), the better. > Tegra30 has more options. > _______________________________________________ > devicetree-discuss mailing list -> devicetree-discuss@lists.ozlabs.org +> devicetree-discuss at lists.ozlabs.org > https://lists.ozlabs.org/listinfo/devicetree-discuss > diff --git a/a/content_digest b/N1/content_digest index ef2a3e8..350096a 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,19 +5,10 @@ "ref\04FD763C5.3090500@wwwdotorg.org\0" "ref\020120612172041.GA28010@avionic-0098.adnet.avionic-design.de\0" "ref\04FD7A36B.9090409@wwwdotorg.org\0" - "From\0Mitch Bradley <wmb@firmworks.com>\0" - "Subject\0Re: [PATCH v2 07/10] ARM: tegra: pcie: Add device tree support\0" + "From\0wmb@firmworks.com (Mitch Bradley)\0" + "Subject\0[PATCH v2 07/10] ARM: tegra: pcie: Add device tree support\0" "Date\0Tue, 12 Jun 2012 11:11:33 -1000\0" - "To\0Stephen Warren <swarren@wwwdotorg.org>\0" - "Cc\0Thierry Reding <thierry.reding@avionic-design.de>" - Russell King <linux@arm.linux.org.uk> - linux-pci@vger.kernel.org - devicetree-discuss@lists.ozlabs.org - Rob Herring <rob.herring@calxeda.com> - Jesse Barnes <jbarnes@virtuousgeek.org> - Colin Cross <ccross@android.com> - linux-tegra@vger.kernel.org - " linux-arm-kernel@lists.infradead.org\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On 6/12/2012 10:15 AM, Stephen Warren wrote:\n" @@ -48,12 +39,12 @@ ">> \t\t#address-cells =<1>;\n" ">> \t\t#size-cells =<1>;\n" ">>\n" - ">> \t\tport@80000000 {\n" + ">> \t\tport at 80000000 {\n" ">> \t\t\treg =<0x80000000 0x00001000>;\n" ">> \t\t\tstatus = \"disabled\";\n" ">> \t\t};\n" ">>\n" - ">> \t\tport@80001000 {\n" + ">> \t\tport at 80001000 {\n" ">> \t\t\treg =<0x80001000 0x00001000>;\n" ">> \t\t\tstatus = \"disabled\";\n" ">> \t\t};\n" @@ -68,7 +59,7 @@ ">\n" "> As a general concept, this kind of design seems OK to me.\n" ">\n" - "> The \"port\" child nodes I think should be named \"pci@...\" given Mitch's\n" + "> The \"port\" child nodes I think should be named \"pci at ...\" given Mitch's\n" "> comments, I think.\n" ">\n" "> The port nodes probably need two entries in reg, given the following in\n" @@ -97,12 +88,12 @@ "> PCIe controller's register space based on the ID using code roughly like\n" "> what I quoted above:\n" ">\n" - "> \tpci@0 {\n" + "> \tpci at 0 {\n" "> \t\treg =<0>;\n" "> \t\tstatus = \"disabled\";\n" "> \t};\n" ">\n" - "> \tpci@1 {\n" + "> \tpci at 1 {\n" "> \t\treg =<0>;\n" "> \t\tstatus = \"disabled\";\n" "> \t};\n" @@ -133,8 +124,8 @@ "> Tegra30 has more options.\n" "> _______________________________________________\n" "> devicetree-discuss mailing list\n" - "> devicetree-discuss@lists.ozlabs.org\n" + "> devicetree-discuss at lists.ozlabs.org\n" "> https://lists.ozlabs.org/listinfo/devicetree-discuss\n" > -d7c64fdf08a34d27e4efce926c3a16546785098f50148fb73743db4586907e73 +ab72d8fcb3799c6f459096c989ec9a1ed25f766097d73564c28701ca7cb1bf9c
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.