diff for duplicates of <20150618205236.9112.20427@quantum> diff --git a/a/1.txt b/N1/1.txt index 66ff6f7..fab91a3 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,51 +1,39 @@ Quoting Boris Brezillon (2015-06-18 12:47:29) > Hi Mike, -> = - +> > On Thu, 18 Jun 2015 11:36:54 -0700 > Michael Turquette <mturquette@linaro.org> wrote: -> = - +> > > Quoting Gregory CLEMENT (2015-06-17 04:57:08) > > > Hi Mike, Stephen, -> > > = - +> > > > > > On 16/06/2015 17:56, Boris Brezillon wrote: -> > > > The crypto SRAM, used by the armada 370 cpuidle code to workaround = -a bug +> > > > The crypto SRAM, used by the armada 370 cpuidle code to workaround a bug > > > > in the BootROM code, requires the crypto clk to be up and running. > > > > Flag the crypto clk as IGNORE_UNUSED until we add the proper -> > > > infrastructure to define the crypto SRAM in the DT and reference th= -e crypto +> > > > infrastructure to define the crypto SRAM in the DT and reference the crypto > > > > clk in this SRAM node. -> > > > = - +> > > > > > > > Reported-by: Kevin Hilman <khilman@linaro.org> > > > > Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com> > > > > Tested-by: Kevin Hilman <khilman@linaro.org> > > > > Fixes: 29e623475c50267ee3aaa49ebb6cbe107bce8d2a ("clk: mvebu: add > > > > missing CESA gate clk"). > > > > Cc: <stable@vger.kernel.org> #4.1 -> > > = - +> > > > > > Acked-by: Gregory CLEMENT <gregory.clement@free-electrons.com> -> > > = - +> > > > > > Would it possible to apply this fix on 4.1-rc8 ? -> > = - +> > > > Hi Gregory, -> > = - +> > > > I'm a bit confused by this. This patch fixes "clk: mvebu: add missing > > CESA gate clk", right? That patch lives in clk-next. It was not pushed > > to Linus' tree yet via a -fixes branch. -> > = - +> > > > Thus I can just apply this patch to clk-next and the problem should be > > resolved in clk-next, no? -> = - +> > Yes. I've tagged this patch as applicable on stable 4.1 in case it > didn't make it in the next -rc (which should be the last one before > 4.1 is released). @@ -58,26 +46,19 @@ Mike > I don't know if it's a good practice, but I've had several fixes which > missed the targeted release in the past, and tagging them as stable > helps in getting the patches applied afterwards. -> = - -> > = - +> +> > > > Furthermore, I do not have 29e623475c50267ee3aaa49ebb6cbe107bce8d2a > > anywhere in my tree. I'm not sure where this sha1 hash came from. -> = - +> > Oops, I mixed the commit hash in my local branch and the one in clk-next > (4d52b2acefdfceae0e47ed08324a96f511dc80b1). -> = - +> > Best Regards, -> = - +> > Boris -> = - -> -- = - +> +> -- > Boris Brezillon, Free Electrons > Embedded Linux and Kernel engineering > http://free-electrons.com diff --git a/a/content_digest b/N1/content_digest index edaf92b..a90fa6a 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,75 +2,48 @@ "ref\055816094.2020208@free-electrons.com\0" "ref\020150618183654.25948.26168@quantum\0" "ref\020150618214729.41acfb07@bbrezillon\0" - "From\0Michael Turquette <mturquette@linaro.org>\0" - "Subject\0Re: [PATCH v2] clk: mvebu: flag the crypto clk as CLK_IGNORE_UNUSED\0" + "From\0mturquette@linaro.org (Michael Turquette)\0" + "Subject\0[PATCH v2] clk: mvebu: flag the crypto clk as CLK_IGNORE_UNUSED\0" "Date\0Thu, 18 Jun 2015 13:52:36 -0700\0" - "To\0Boris Brezillon <boris.brezillon@free-electrons.com>" - "\0" - "Cc\0Gregory CLEMENT <gregory.clement@free-electrons.com>" - Stephen Boyd <sboyd@codeaurora.org> - Thomas Petazzoni <thomas.petazzoni@free-electrons.com> - Jason Cooper <jason@lakedaemon.net> - Tawfik Bayouk <tawfik@marvell.com> - Andrew Lunn <andrew@lunn.ch> - Kevin Hilman <khilman@kernel.org> - stable@vger.kernel.org - Eran Ben-Avi <benavi@marvell.com> - Nadav Haklai <nadavh@marvell.com> - Lior Amsalem <alior@marvell.com> - linux-clk@vger.kernel.org - linux-arm-kernel@lists.infradead.org - " Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "Quoting Boris Brezillon (2015-06-18 12:47:29)\n" "> Hi Mike,\n" - "> =\n" - "\n" + "> \n" "> On Thu, 18 Jun 2015 11:36:54 -0700\n" "> Michael Turquette <mturquette@linaro.org> wrote:\n" - "> =\n" - "\n" + "> \n" "> > Quoting Gregory CLEMENT (2015-06-17 04:57:08)\n" "> > > Hi Mike, Stephen,\n" - "> > > =\n" - "\n" + "> > > \n" "> > > On 16/06/2015 17:56, Boris Brezillon wrote:\n" - "> > > > The crypto SRAM, used by the armada 370 cpuidle code to workaround =\n" - "a bug\n" + "> > > > The crypto SRAM, used by the armada 370 cpuidle code to workaround a bug\n" "> > > > in the BootROM code, requires the crypto clk to be up and running.\n" "> > > > Flag the crypto clk as IGNORE_UNUSED until we add the proper\n" - "> > > > infrastructure to define the crypto SRAM in the DT and reference th=\n" - "e crypto\n" + "> > > > infrastructure to define the crypto SRAM in the DT and reference the crypto\n" "> > > > clk in this SRAM node.\n" - "> > > > =\n" - "\n" + "> > > > \n" "> > > > Reported-by: Kevin Hilman <khilman@linaro.org>\n" "> > > > Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>\n" "> > > > Tested-by: Kevin Hilman <khilman@linaro.org>\n" "> > > > Fixes: 29e623475c50267ee3aaa49ebb6cbe107bce8d2a (\"clk: mvebu: add\n" "> > > > missing CESA gate clk\").\n" "> > > > Cc: <stable@vger.kernel.org> #4.1\n" - "> > > =\n" - "\n" + "> > > \n" "> > > Acked-by: Gregory CLEMENT <gregory.clement@free-electrons.com>\n" - "> > > =\n" - "\n" + "> > > \n" "> > > Would it possible to apply this fix on 4.1-rc8 ?\n" - "> > =\n" - "\n" + "> > \n" "> > Hi Gregory,\n" - "> > =\n" - "\n" + "> > \n" "> > I'm a bit confused by this. This patch fixes \"clk: mvebu: add missing\n" "> > CESA gate clk\", right? That patch lives in clk-next. It was not pushed\n" "> > to Linus' tree yet via a -fixes branch.\n" - "> > =\n" - "\n" + "> > \n" "> > Thus I can just apply this patch to clk-next and the problem should be\n" "> > resolved in clk-next, no?\n" - "> =\n" - "\n" + "> \n" "> Yes. I've tagged this patch as applicable on stable 4.1 in case it\n" "> didn't make it in the next -rc (which should be the last one before\n" "> 4.1 is released).\n" @@ -83,28 +56,21 @@ "> I don't know if it's a good practice, but I've had several fixes which\n" "> missed the targeted release in the past, and tagging them as stable\n" "> helps in getting the patches applied afterwards.\n" - "> =\n" - "\n" - "> > =\n" - "\n" + "> \n" + "> > \n" "> > Furthermore, I do not have 29e623475c50267ee3aaa49ebb6cbe107bce8d2a\n" "> > anywhere in my tree. I'm not sure where this sha1 hash came from.\n" - "> =\n" - "\n" + "> \n" "> Oops, I mixed the commit hash in my local branch and the one in clk-next\n" "> (4d52b2acefdfceae0e47ed08324a96f511dc80b1).\n" - "> =\n" - "\n" + "> \n" "> Best Regards,\n" - "> =\n" - "\n" + "> \n" "> Boris\n" - "> =\n" - "\n" - "> -- =\n" - "\n" + "> \n" + "> -- \n" "> Boris Brezillon, Free Electrons\n" "> Embedded Linux and Kernel engineering\n" > http://free-electrons.com -4effc91466a19bca43fe99a268070e37a6499e3a1e71e7b0b10dec1ddb3b1c9f +62c962f65835db105068794dd11e36bdc9624b8787c1ecd6a136727412d9b7ba
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.