diff for duplicates of <20150218092225.GE21937@kwain> diff --git a/a/1.txt b/N1/1.txt index ef43861..1d9a01d 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -41,7 +41,7 @@ On Wed, Feb 18, 2015 at 09:09:58AM +0000, Lee Jones 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>; @@ -77,14 +77,14 @@ the devices using them. > 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"; > }; > }; @@ -94,7 +94,7 @@ That's exactly the point of this series: having one sub-node per device. 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>; @@ -124,6 +124,6 @@ chip: chip-controller at ea0000 { Antoine -- -Antoine T?nart, Free Electrons +Antoine Ténart, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com diff --git a/a/content_digest b/N1/content_digest index 7fd2e72..531fa60 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,10 +5,17 @@ "ref\020150217115447.GA3989@x1\0" "ref\020150218084004.GD21937@kwain\0" "ref\020150218090958.GA18042@x1\0" - "From\0antoine.tenart@free-electrons.com (Antoine Tenart)\0" - "Subject\0[PATCH 01/11] mfd: add the Berlin controller driver\0" + "From\0Antoine Tenart <antoine.tenart@free-electrons.com>\0" + "Subject\0Re: [PATCH 01/11] mfd: add the Berlin controller driver\0" "Date\0Wed, 18 Feb 2015 10:22:25 +0100\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Lee Jones <lee.jones@linaro.org>\0" + "Cc\0Antoine Tenart <antoine.tenart@free-electrons.com>" + sebastian.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, Feb 18, 2015 at 09:09:58AM +0000, Lee Jones wrote:\n" @@ -54,7 +61,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" @@ -90,14 +97,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" @@ -107,7 +114,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" @@ -137,8 +144,8 @@ "Antoine\n" "\n" "-- \n" - "Antoine T?nart, Free Electrons\n" + "Antoine T\303\251nart, Free Electrons\n" "Embedded Linux, Kernel and Android engineering\n" http://free-electrons.com -91d67fc273cb3464e107f680be77f737c6b940bdc27d75178c49bc63202e0cef +ba93411a5a75ecc1356f174ac2e89e4b6c02ba4e931cda2968f97a553dd88fca
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.