diff for duplicates of <20151022101116.20687.55089@quantum> diff --git a/a/1.txt b/N1/1.txt index c141b0f..8b49764 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,36 +1,26 @@ Quoting Scott Wood (2015-10-09 16:57:44) > On Thu, 2015-10-01 at 19:26 -0500, Scott Wood wrote: > > [Resending to updated e-mail address] -> > = - +> > > > On Tue, 2015-08-11 at 11:25 -0700, Michael Turquette wrote: > > > Hi Scott, -> > > = - +> > > > > > Quoting Scott Wood (2015-06-18 19:49:10) -> > > > The existing device tree bindings are error-prone and inflexible. = - +> > > > The existing device tree bindings are error-prone and inflexible. > > > > Correct the mistake by moving the knowledge into the driver, which -> > > > has more flexibility in describing the quirks of each chip. This l= -eaves -> > > > the device tree to its proper role of identifying a programming = - +> > > > has more flexibility in describing the quirks of each chip. This leaves +> > > > the device tree to its proper role of identifying a programming > > > > interface > > > > rather than describing its individual registers. -> > > = - +> > > > > > Sorry for not responding to this one sooner. Fell through the cracks. -> > > = - -> > > All of the changes to drives/clk/clk-qoriq.c look great to me. I assu= -me +> > > +> > > All of the changes to drives/clk/clk-qoriq.c look great to me. I assume > > > you need to keep all of these patches together and want to the take > > > through the freescale tree? If so feel free to add, -> > > = - +> > > > > > Acked-by: Michael Turquette <mturquette@baylibre.com> -> > = - +> > > > Is the ack still valid for the v3 patchset? Yes. Looks Stephen beat me to it though. @@ -38,10 +28,8 @@ Yes. Looks Stephen beat me to it though. Regards, Mike -> = - +> > ping -> = - +> > -Scott ->=20 +> diff --git a/a/content_digest b/N1/content_digest index dc01ae2..7fa80a2 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,53 +5,42 @@ "From\0Michael Turquette <mturquette@baylibre.com>\0" "Subject\0Re: [RFC PATCH 0/8] clk: qoriq: Move chip-specific knowledge into driver\0" "Date\0Thu, 22 Oct 2015 03:11:16 -0700\0" - "To\0Scott Wood <scottwood@freescale.com>" - "\0" - "Cc\0Stephen Boyd <sboyd@codeaurora.org>" - Tang Yuantian <Yuantian.Tang@freescale.com> - Rafael J. Wysocki <rjw@rjwysocki.net> + "To\0Scott Wood <scottwood@freescale.com>\0" + "Cc\0devicetree@vger.kernel.org" Liberman Igal-B31950 <Igal.Liberman@freescale.com> - Bucur Madalin-Cristian-B32716 <madalin.bucur@freescale.com> - linux-clk@vger.kernel.org + Rafael J. Wysocki <rjw@rjwysocki.net> linux-pm@vger.kernel.org + Stephen Boyd <sboyd@codeaurora.org> + Tang Yuantian <Yuantian.Tang@freescale.com> linuxppc-dev@lists.ozlabs.org + linux-clk@vger.kernel.org linux-arm-kernel@lists.infradead.org - " devicetree@vger.kernel.org\0" + " Bucur Madalin-Cristian-B32716 <madalin.bucur@freescale.com>\0" "\00:1\0" "b\0" "Quoting Scott Wood (2015-10-09 16:57:44)\n" "> On Thu, 2015-10-01 at 19:26 -0500, Scott Wood wrote:\n" "> > [Resending to updated e-mail address]\n" - "> > =\n" - "\n" + "> > \n" "> > On Tue, 2015-08-11 at 11:25 -0700, Michael Turquette wrote:\n" "> > > Hi Scott,\n" - "> > > =\n" - "\n" + "> > > \n" "> > > Quoting Scott Wood (2015-06-18 19:49:10)\n" - "> > > > The existing device tree bindings are error-prone and inflexible. =\n" - "\n" + "> > > > The existing device tree bindings are error-prone and inflexible. \n" "> > > > Correct the mistake by moving the knowledge into the driver, which\n" - "> > > > has more flexibility in describing the quirks of each chip. This l=\n" - "eaves\n" - "> > > > the device tree to its proper role of identifying a programming =\n" - "\n" + "> > > > has more flexibility in describing the quirks of each chip. This leaves\n" + "> > > > the device tree to its proper role of identifying a programming \n" "> > > > interface\n" "> > > > rather than describing its individual registers.\n" - "> > > =\n" - "\n" + "> > > \n" "> > > Sorry for not responding to this one sooner. Fell through the cracks.\n" - "> > > =\n" - "\n" - "> > > All of the changes to drives/clk/clk-qoriq.c look great to me. I assu=\n" - "me\n" + "> > > \n" + "> > > All of the changes to drives/clk/clk-qoriq.c look great to me. I assume\n" "> > > you need to keep all of these patches together and want to the take\n" "> > > through the freescale tree? If so feel free to add,\n" - "> > > =\n" - "\n" + "> > > \n" "> > > Acked-by: Michael Turquette <mturquette@baylibre.com>\n" - "> > =\n" - "\n" + "> > \n" "> > Is the ack still valid for the v3 patchset?\n" "\n" "Yes. Looks Stephen beat me to it though.\n" @@ -59,12 +48,10 @@ "Regards,\n" "Mike\n" "\n" - "> =\n" - "\n" + "> \n" "> ping\n" - "> =\n" - "\n" + "> \n" "> -Scott\n" - >=20 + > -fbd8726229d3783d50104787fd7cb14cef84fd5928e710da289e341ed9e3cc03 +05c3fa6eb8e2a1521cfb49131534157bd2e04de55f4beb2c3ccdd05feaf2de35
diff --git a/a/1.txt b/N2/1.txt index c141b0f..8b49764 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,36 +1,26 @@ Quoting Scott Wood (2015-10-09 16:57:44) > On Thu, 2015-10-01 at 19:26 -0500, Scott Wood wrote: > > [Resending to updated e-mail address] -> > = - +> > > > On Tue, 2015-08-11 at 11:25 -0700, Michael Turquette wrote: > > > Hi Scott, -> > > = - +> > > > > > Quoting Scott Wood (2015-06-18 19:49:10) -> > > > The existing device tree bindings are error-prone and inflexible. = - +> > > > The existing device tree bindings are error-prone and inflexible. > > > > Correct the mistake by moving the knowledge into the driver, which -> > > > has more flexibility in describing the quirks of each chip. This l= -eaves -> > > > the device tree to its proper role of identifying a programming = - +> > > > has more flexibility in describing the quirks of each chip. This leaves +> > > > the device tree to its proper role of identifying a programming > > > > interface > > > > rather than describing its individual registers. -> > > = - +> > > > > > Sorry for not responding to this one sooner. Fell through the cracks. -> > > = - -> > > All of the changes to drives/clk/clk-qoriq.c look great to me. I assu= -me +> > > +> > > All of the changes to drives/clk/clk-qoriq.c look great to me. I assume > > > you need to keep all of these patches together and want to the take > > > through the freescale tree? If so feel free to add, -> > > = - +> > > > > > Acked-by: Michael Turquette <mturquette@baylibre.com> -> > = - +> > > > Is the ack still valid for the v3 patchset? Yes. Looks Stephen beat me to it though. @@ -38,10 +28,8 @@ Yes. Looks Stephen beat me to it though. Regards, Mike -> = - +> > ping -> = - +> > -Scott ->=20 +> diff --git a/a/content_digest b/N2/content_digest index dc01ae2..d6965a1 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -2,56 +2,35 @@ "ref\020150811182535.31346.52965@quantum\0" "ref\01443745589.5336.185.camel@freescale.com\0" "ref\01444435064.5185.16.camel@freescale.com\0" - "From\0Michael Turquette <mturquette@baylibre.com>\0" - "Subject\0Re: [RFC PATCH 0/8] clk: qoriq: Move chip-specific knowledge into driver\0" + "From\0mturquette@baylibre.com (Michael Turquette)\0" + "Subject\0[RFC PATCH 0/8] clk: qoriq: Move chip-specific knowledge into driver\0" "Date\0Thu, 22 Oct 2015 03:11:16 -0700\0" - "To\0Scott Wood <scottwood@freescale.com>" - "\0" - "Cc\0Stephen Boyd <sboyd@codeaurora.org>" - Tang Yuantian <Yuantian.Tang@freescale.com> - Rafael J. Wysocki <rjw@rjwysocki.net> - Liberman Igal-B31950 <Igal.Liberman@freescale.com> - Bucur Madalin-Cristian-B32716 <madalin.bucur@freescale.com> - linux-clk@vger.kernel.org - linux-pm@vger.kernel.org - linuxppc-dev@lists.ozlabs.org - linux-arm-kernel@lists.infradead.org - " devicetree@vger.kernel.org\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "Quoting Scott Wood (2015-10-09 16:57:44)\n" "> On Thu, 2015-10-01 at 19:26 -0500, Scott Wood wrote:\n" "> > [Resending to updated e-mail address]\n" - "> > =\n" - "\n" + "> > \n" "> > On Tue, 2015-08-11 at 11:25 -0700, Michael Turquette wrote:\n" "> > > Hi Scott,\n" - "> > > =\n" - "\n" + "> > > \n" "> > > Quoting Scott Wood (2015-06-18 19:49:10)\n" - "> > > > The existing device tree bindings are error-prone and inflexible. =\n" - "\n" + "> > > > The existing device tree bindings are error-prone and inflexible. \n" "> > > > Correct the mistake by moving the knowledge into the driver, which\n" - "> > > > has more flexibility in describing the quirks of each chip. This l=\n" - "eaves\n" - "> > > > the device tree to its proper role of identifying a programming =\n" - "\n" + "> > > > has more flexibility in describing the quirks of each chip. This leaves\n" + "> > > > the device tree to its proper role of identifying a programming \n" "> > > > interface\n" "> > > > rather than describing its individual registers.\n" - "> > > =\n" - "\n" + "> > > \n" "> > > Sorry for not responding to this one sooner. Fell through the cracks.\n" - "> > > =\n" - "\n" - "> > > All of the changes to drives/clk/clk-qoriq.c look great to me. I assu=\n" - "me\n" + "> > > \n" + "> > > All of the changes to drives/clk/clk-qoriq.c look great to me. I assume\n" "> > > you need to keep all of these patches together and want to the take\n" "> > > through the freescale tree? If so feel free to add,\n" - "> > > =\n" - "\n" + "> > > \n" "> > > Acked-by: Michael Turquette <mturquette@baylibre.com>\n" - "> > =\n" - "\n" + "> > \n" "> > Is the ack still valid for the v3 patchset?\n" "\n" "Yes. Looks Stephen beat me to it though.\n" @@ -59,12 +38,10 @@ "Regards,\n" "Mike\n" "\n" - "> =\n" - "\n" + "> \n" "> ping\n" - "> =\n" - "\n" + "> \n" "> -Scott\n" - >=20 + > -fbd8726229d3783d50104787fd7cb14cef84fd5928e710da289e341ed9e3cc03 +9227c53dbb38ca2e575b70d0a726c266984e319e99f059dbfafe7d15e2db675d
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.