diff for duplicates of <20150218104023.GA22296@x1> diff --git a/a/1.txt b/N1/1.txt index 4729851..8c376a9 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -43,7 +43,7 @@ On Wed, 18 Feb 2015, Antoine Tenart wrote: > > > So we had a single node, chip-controller, accessed by multiple > > > devices -and drivers-. We ended up with: > > > -> > > chip: chip-control at ea0000 { +> > > chip: chip-control@ea0000 { > > > compatible = "marvell,berlin2q-chip-ctrl"; > > > reg = <0xea0000 0x400>, <0xdd0170 0x10>; > > > #clock-cells = <1>; @@ -79,14 +79,14 @@ On Wed, 18 Feb 2015, Antoine Tenart wrote: > > > If so, I would expect to see something like: > > -> > control at ea0000 { +> > control@ea0000 { > > compatible = "marvel,control"; > > -> > pinctrl at xxxxx { +> > pinctrl@xxxxx { > > compatible = "marvel,pinctrl"; > > }; > > -> > reset at xxxxx { +> > reset@xxxxx { > > compatible = "marvel,reset"; > > }; > > }; @@ -96,7 +96,7 @@ On Wed, 18 Feb 2015, Antoine Tenart wrote: > With this series applied, we have (the clock being a sub-node of the > chip-controller node is part of another series following this one): > -> chip: chip-controller at ea0000 { +> chip: chip-controller@ea0000 { > compatible = "marvell,berlin2q-chip-ctrl", "syscon"; > reg = <0xea0000 0x400>, <0xdd0170 0x10>; > #clock-cells = <1>; @@ -134,5 +134,5 @@ why do you think this is necessary? -- Lee Jones Linaro STMicroelectronics Landing Team Lead -Linaro.org ? Open source software for ARM SoCs +Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog diff --git a/a/content_digest b/N1/content_digest index 8eeeb1d..22bb868 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -6,10 +6,16 @@ "ref\020150218084004.GD21937@kwain\0" "ref\020150218090958.GA18042@x1\0" "ref\020150218092225.GE21937@kwain\0" - "From\0lee.jones@linaro.org (Lee Jones)\0" - "Subject\0[PATCH 01/11] mfd: add the Berlin controller driver\0" + "From\0Lee Jones <lee.jones@linaro.org>\0" + "Subject\0Re: [PATCH 01/11] mfd: add the Berlin controller driver\0" "Date\0Wed, 18 Feb 2015 10:40:23 +0000\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Antoine Tenart <antoine.tenart@free-electrons.com>\0" + "Cc\0sebastian.hesselbarth@gmail.com" + sameo@linux.intel.com + jszhang@marvell.com + zmxu@marvell.com + linux-arm-kernel@lists.infradead.org + " linux-kernel@vger.kernel.org\0" "\00:1\0" "b\0" "On Wed, 18 Feb 2015, Antoine Tenart wrote:\n" @@ -57,7 +63,7 @@ "> > > So we had a single node, chip-controller, accessed by multiple\n" "> > > devices -and drivers-. We ended up with:\n" "> > > \n" - "> > > chip: chip-control at ea0000 {\n" + "> > > chip: chip-control@ea0000 {\n" "> > > \tcompatible = \"marvell,berlin2q-chip-ctrl\";\n" "> > > \treg = <0xea0000 0x400>, <0xdd0170 0x10>;\n" "> > > \t#clock-cells = <1>;\n" @@ -93,14 +99,14 @@ "> \n" "> > If so, I would expect to see something like:\n" "> > \n" - "> > control at ea0000 {\n" + "> > control@ea0000 {\n" "> > \tcompatible = \"marvel,control\";\n" "> > \n" - "> > \tpinctrl at xxxxx {\n" + "> > \tpinctrl@xxxxx {\n" "> > \t\tcompatible = \"marvel,pinctrl\";\n" "> > \t};\n" "> > \n" - "> > \treset at xxxxx {\n" + "> > \treset@xxxxx {\n" "> > \t\tcompatible = \"marvel,reset\";\n" "> > \t};\n" "> > };\n" @@ -110,7 +116,7 @@ "> With this series applied, we have (the clock being a sub-node of the\n" "> chip-controller node is part of another series following this one):\n" "> \n" - "> chip: chip-controller at ea0000 {\n" + "> chip: chip-controller@ea0000 {\n" "> compatible = \"marvell,berlin2q-chip-ctrl\", \"syscon\";\n" "> reg = <0xea0000 0x400>, <0xdd0170 0x10>;\n" "> #clock-cells = <1>;\n" @@ -148,7 +154,7 @@ "-- \n" "Lee Jones\n" "Linaro STMicroelectronics Landing Team Lead\n" - "Linaro.org ? Open source software for ARM SoCs\n" + "Linaro.org \342\224\202 Open source software for ARM SoCs\n" Follow Linaro: Facebook | Twitter | Blog -dd90a0c90631854499052c8bc3ed2d8b163cca2c0bd6192ee70d50ab5bd5ebca +bd61131d046d5a4ca76ad63b16c31efe0e3f7f7e8876d4a07f234da8ea6d92d7
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.