diff for duplicates of <46532903.ghnH4Us8Zz@avalon> diff --git a/a/1.txt b/N1/1.txt index 789707e..439a88e 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -7,7 +7,7 @@ On Thursday 27 March 2014 14:57:56 Sylwester Nawrocki wrote: > >> as specified in clock-parents, clock-rates DT properties for a consumer > >> device and a call to it before driver is bound to a device. > >> -> >> Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com> +> >> Signed-off-by: Sylwester Nawrocki <s.nawrocki-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org> > >> --- > > [...] @@ -46,7 +46,7 @@ On Thursday 27 March 2014 14:57:56 Sylwester Nawrocki wrote: > >> the > >> +latter the list of assigned clock frequency values (one cell each). > >> + -> >> + uart at a000 { +> >> + uart@a000 { > >> + compatible = "fsl,imx-uart"; > >> + reg = <0xa000 0x1000>; > >> + ... @@ -67,7 +67,7 @@ On Thursday 27 March 2014 14:57:56 Sylwester Nawrocki wrote: > > printed ? > > In general, the assumption is that the <&clkcon 3> clock would be used only -> by the uart at a000 device. +> by the uart@a000 device. OK. Removing the problem is a simple way to fix it :-) What about stating this explicitly in the documentation then ? Maybe by prefixing your proposed @@ -126,3 +126,8 @@ to support the discussion. Regards, Laurent Pinchart + +-- +To unsubscribe from this list: send the line "unsubscribe devicetree" in +the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index ba0ccfc..5490236 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,10 +1,25 @@ "ref\01395922579-28547-1-git-send-email-s.nawrocki@samsung.com\0" "ref\077553409.zvN7VkNGe7@avalon\0" "ref\053342E64.5060505@samsung.com\0" - "From\0laurent.pinchart@ideasonboard.com (Laurent Pinchart)\0" - "Subject\0[PATCH RFC v3 2/2] clk: Add handling of clk parent and rate assigned from DT\0" + "ref\053342E64.5060505-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org\0" + "From\0Laurent Pinchart <laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>\0" + "Subject\0Re: [PATCH RFC v3 2/2] clk: Add handling of clk parent and rate assigned from DT\0" "Date\0Thu, 27 Mar 2014 15:08:10 +0100\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Sylwester Nawrocki <s.nawrocki-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>\0" + "Cc\0linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" + mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org + mark.rutland-5wv7dgnIgG8@public.gmane.org + devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org + gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org + t.figa-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org + sw0312.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org + linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org + robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org + galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org + grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org + " m.szyprowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org\0" "\00:1\0" "b\0" "Hi Sylwester,\n" @@ -16,7 +31,7 @@ "> >> as specified in clock-parents, clock-rates DT properties for a consumer\n" "> >> device and a call to it before driver is bound to a device.\n" "> >> \n" - "> >> Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>\n" + "> >> Signed-off-by: Sylwester Nawrocki <s.nawrocki-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>\n" "> >> ---\n" "> \n" "> [...]\n" @@ -55,7 +70,7 @@ "> >> the\n" "> >> +latter the list of assigned clock frequency values (one cell each).\n" "> >> +\n" - "> >> + uart at a000 {\n" + "> >> + uart@a000 {\n" "> >> + compatible = \"fsl,imx-uart\";\n" "> >> + reg = <0xa000 0x1000>;\n" "> >> + ...\n" @@ -76,7 +91,7 @@ "> > printed ?\n" "> \n" "> In general, the assumption is that the <&clkcon 3> clock would be used only\n" - "> by the uart at a000 device.\n" + "> by the uart@a000 device.\n" "\n" "OK. Removing the problem is a simple way to fix it :-) What about stating this \n" "explicitly in the documentation then ? Maybe by prefixing your proposed \n" @@ -134,6 +149,11 @@ "-- \n" "Regards,\n" "\n" - Laurent Pinchart + "Laurent Pinchart\n" + "\n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe devicetree\" in\n" + "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -a1fb3b32910db2166fe2c008f1e1a77061baa4ef833e4529707b465c1fc6ff2d +d3aebb4355e9681516baaece21c625f5f8de235cc00288759b85f8a3a87fb14b
diff --git a/a/1.txt b/N2/1.txt index 789707e..8ee37b7 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -46,7 +46,7 @@ On Thursday 27 March 2014 14:57:56 Sylwester Nawrocki wrote: > >> the > >> +latter the list of assigned clock frequency values (one cell each). > >> + -> >> + uart at a000 { +> >> + uart@a000 { > >> + compatible = "fsl,imx-uart"; > >> + reg = <0xa000 0x1000>; > >> + ... @@ -67,7 +67,7 @@ On Thursday 27 March 2014 14:57:56 Sylwester Nawrocki wrote: > > printed ? > > In general, the assumption is that the <&clkcon 3> clock would be used only -> by the uart at a000 device. +> by the uart@a000 device. OK. Removing the problem is a simple way to fix it :-) What about stating this explicitly in the documentation then ? Maybe by prefixing your proposed diff --git a/a/content_digest b/N2/content_digest index ba0ccfc..68a2e34 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,10 +1,24 @@ "ref\01395922579-28547-1-git-send-email-s.nawrocki@samsung.com\0" "ref\077553409.zvN7VkNGe7@avalon\0" "ref\053342E64.5060505@samsung.com\0" - "From\0laurent.pinchart@ideasonboard.com (Laurent Pinchart)\0" - "Subject\0[PATCH RFC v3 2/2] clk: Add handling of clk parent and rate assigned from DT\0" + "From\0Laurent Pinchart <laurent.pinchart@ideasonboard.com>\0" + "Subject\0Re: [PATCH RFC v3 2/2] clk: Add handling of clk parent and rate assigned from DT\0" "Date\0Thu, 27 Mar 2014 15:08:10 +0100\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Sylwester Nawrocki <s.nawrocki@samsung.com>\0" + "Cc\0linux-arm-kernel@lists.infradead.org" + mturquette@linaro.org + mark.rutland@arm.com + devicetree@vger.kernel.org + linux@arm.linux.org.uk + gregkh@linuxfoundation.org + t.figa@samsung.com + sw0312.kim@samsung.com + linux-kernel@vger.kernel.org + kyungmin.park@samsung.com + robh+dt@kernel.org + galak@codeaurora.org + grant.likely@linaro.org + " m.szyprowski@samsung.com\0" "\00:1\0" "b\0" "Hi Sylwester,\n" @@ -55,7 +69,7 @@ "> >> the\n" "> >> +latter the list of assigned clock frequency values (one cell each).\n" "> >> +\n" - "> >> + uart at a000 {\n" + "> >> + uart@a000 {\n" "> >> + compatible = \"fsl,imx-uart\";\n" "> >> + reg = <0xa000 0x1000>;\n" "> >> + ...\n" @@ -76,7 +90,7 @@ "> > printed ?\n" "> \n" "> In general, the assumption is that the <&clkcon 3> clock would be used only\n" - "> by the uart at a000 device.\n" + "> by the uart@a000 device.\n" "\n" "OK. Removing the problem is a simple way to fix it :-) What about stating this \n" "explicitly in the documentation then ? Maybe by prefixing your proposed \n" @@ -136,4 +150,4 @@ "\n" Laurent Pinchart -a1fb3b32910db2166fe2c008f1e1a77061baa4ef833e4529707b465c1fc6ff2d +58f90d7e89b357e177779298cb8d6770f118842a49db8ce99cc346cd8bb7d146
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.