diff for duplicates of <5150DDDD.9010904@wwwdotorg.org> diff --git a/a/1.txt b/N1/1.txt index d96a774..5b08ced 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,8 +1,8 @@ -On 03/22/2013 04:41 PM, S?ren Brinkmann wrote: +On 03/22/2013 04:41 PM, Sören Brinkmann wrote: > Hi Lars, > > On Thu, Mar 21, 2013 at 07:32:52PM +0100, Lars-Peter Clausen wrote: ->> On 03/21/2013 12:56 AM, S?ren Brinkmann wrote: +>> On 03/21/2013 12:56 AM, Sören Brinkmann wrote: >>> Hi, >>> >>> I spent some time working on this and incorporating feedback. Here's an updated proposal for a clock controller for Zynq: @@ -49,3 +49,7 @@ represented by a separate DT node, right? The issue with parent clock names is simply a red herring. A solution is needed to registered clock with a parent clock object, rather than a parent clock name. Then, the parent names are completely irrelevant. +_______________________________________________ +devicetree-discuss mailing list +devicetree-discuss@lists.ozlabs.org +https://lists.ozlabs.org/listinfo/devicetree-discuss diff --git a/a/content_digest b/N1/content_digest index c5db565..5804c21 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,17 +1,29 @@ "ref\027dae808-1d3a-4001-8eb2-b0a6e2a34b8f@AM1EHSMHS013.ehs.local\0" "ref\0514B5254.50101@metafoo.de\0" "ref\0128fc723-ace7-4f4c-95d9-971b42a52080@CH1EHSMHS028.ehs.local\0" - "From\0swarren@wwwdotorg.org (Stephen Warren)\0" - "Subject\0RFC v2: Zynq Clock Controller\0" + "ref\0128fc723-ace7-4f4c-95d9-971b42a52080-p/+QeVIcf1ANTaRkHJHP0bjjLBE8jN/0@public.gmane.org\0" + "From\0Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>\0" + "Subject\0Re: RFC v2: Zynq Clock Controller\0" "Date\0Mon, 25 Mar 2013 17:29:33 -0600\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0S\303\266ren Brinkmann <soren.brinkmann-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>\0" + "Cc\0Josh Cartwright <josh.cartwright-acOepvfBmUk@public.gmane.org>" + Mike Turquette <mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> + " Jan L\303\274bbe <jlu-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>" + devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org + Michal Simek <michal.simek-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org> + linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + Lars-Peter Clausen <lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org> + git-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org + Peter Crosthwaite <pcrost-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org> + Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> + " linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org\0" "\00:1\0" "b\0" - "On 03/22/2013 04:41 PM, S?ren Brinkmann wrote:\n" + "On 03/22/2013 04:41 PM, S\303\266ren Brinkmann wrote:\n" "> Hi Lars,\n" "> \n" "> On Thu, Mar 21, 2013 at 07:32:52PM +0100, Lars-Peter Clausen wrote:\n" - ">> On 03/21/2013 12:56 AM, S?ren Brinkmann wrote:\n" + ">> On 03/21/2013 12:56 AM, S\303\266ren Brinkmann wrote:\n" ">>> Hi,\n" ">>>\n" ">>> I spent some time working on this and incorporating feedback. Here's an updated proposal for a clock controller for Zynq:\n" @@ -57,6 +69,10 @@ "\n" "The issue with parent clock names is simply a red herring. A solution is\n" "needed to registered clock with a parent clock object, rather than a\n" - parent clock name. Then, the parent names are completely irrelevant. + "parent clock name. Then, the parent names are completely irrelevant.\n" + "_______________________________________________\n" + "devicetree-discuss mailing list\n" + "devicetree-discuss@lists.ozlabs.org\n" + https://lists.ozlabs.org/listinfo/devicetree-discuss -47d0af4547bf68598b368710b9a744d385a7aecf3968e9626dbbcaebdf18beef +0a41525b380a38bc4788f40ae8802029b9b4e7b32db74b3db8982b07adf5b0e3
diff --git a/a/1.txt b/N2/1.txt index d96a774..684025e 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,8 +1,8 @@ -On 03/22/2013 04:41 PM, S?ren Brinkmann wrote: +On 03/22/2013 04:41 PM, Sören Brinkmann wrote: > Hi Lars, > > On Thu, Mar 21, 2013 at 07:32:52PM +0100, Lars-Peter Clausen wrote: ->> On 03/21/2013 12:56 AM, S?ren Brinkmann wrote: +>> On 03/21/2013 12:56 AM, Sören Brinkmann wrote: >>> Hi, >>> >>> I spent some time working on this and incorporating feedback. Here's an updated proposal for a clock controller for Zynq: diff --git a/a/content_digest b/N2/content_digest index c5db565..7c2d5b8 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,17 +1,30 @@ "ref\027dae808-1d3a-4001-8eb2-b0a6e2a34b8f@AM1EHSMHS013.ehs.local\0" "ref\0514B5254.50101@metafoo.de\0" "ref\0128fc723-ace7-4f4c-95d9-971b42a52080@CH1EHSMHS028.ehs.local\0" - "From\0swarren@wwwdotorg.org (Stephen Warren)\0" - "Subject\0RFC v2: Zynq Clock Controller\0" + "From\0Stephen Warren <swarren@wwwdotorg.org>\0" + "Subject\0Re: RFC v2: Zynq Clock Controller\0" "Date\0Mon, 25 Mar 2013 17:29:33 -0600\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0S\303\266ren Brinkmann <soren.brinkmann@xilinx.com>\0" + "Cc\0Lars-Peter Clausen <lars@metafoo.de>" + Mike Turquette <mturquette@linaro.org> + Josh Cartwright <josh.cartwright@ni.com> + Michal Simek <michal.simek@xilinx.com> + Peter Crosthwaite <pcrost@xilinx.com> + Prashant Gaikwad <pgaikwad@nvidia.com> + devicetree-discuss@lists.ozlabs.org + linux-kernel@vger.kernel.org + linux-arm-kernel@lists.infradead.org + git@xilinx.com + " Jan L\303\274bbe <jlu@pengutronix.de>" + Sascha Hauer <s.hauer@pengutronix.de> + " Peter De Schrijver <pdeschrijver@nvidia.com>\0" "\00:1\0" "b\0" - "On 03/22/2013 04:41 PM, S?ren Brinkmann wrote:\n" + "On 03/22/2013 04:41 PM, S\303\266ren Brinkmann wrote:\n" "> Hi Lars,\n" "> \n" "> On Thu, Mar 21, 2013 at 07:32:52PM +0100, Lars-Peter Clausen wrote:\n" - ">> On 03/21/2013 12:56 AM, S?ren Brinkmann wrote:\n" + ">> On 03/21/2013 12:56 AM, S\303\266ren Brinkmann wrote:\n" ">>> Hi,\n" ">>>\n" ">>> I spent some time working on this and incorporating feedback. Here's an updated proposal for a clock controller for Zynq:\n" @@ -59,4 +72,4 @@ "needed to registered clock with a parent clock object, rather than a\n" parent clock name. Then, the parent names are completely irrelevant. -47d0af4547bf68598b368710b9a744d385a7aecf3968e9626dbbcaebdf18beef +ae60aa64a6129338731e73728b59fbfdeb20d3e31e133c6d6f10f5996ceb5675
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.