diff for duplicates of <1524473542.4026.26.camel@baylibre.com> diff --git a/a/1.txt b/N1/1.txt index 035bb79..d8f6504 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,5 +1,5 @@ On Sun, 2018-04-22 at 09:43 +0200, Maxime Jourdan wrote: -> Hi Neil, J?rome, +> Hi Neil, Jérome, Beware, replies should also be plain text. Some mailing list will block your mail if it is HTML. @@ -9,7 +9,7 @@ Also, please avoid top posting - instead reply inside the orignal mail or after. > > Thanks for the answers, I'll resubmit with proper formatting. > -> @J?rome: very valid points. The usage of the clk will indeed be through set_clk_rate on the leaf clock within the driver, so I don't need to expose the mux. If I want the mux automatically selected to provide the nearest target clock, should I keep CLK_SET_RATE_NO_REPARENT ? +> @Jérome: very valid points. The usage of the clk will indeed be through set_clk_rate on the leaf clock within the driver, so I don't need to expose the mux. If I want the mux automatically selected to provide the nearest target clock, should I keep CLK_SET_RATE_NO_REPARENT ? > Nope, CLK_SET_RATE_NO_REPARENT tells the clock framework to *keep* the same @@ -258,7 +258,7 @@ Here the rate propagation will stop at the fdiv clocks, since they are fixed. > > > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-clk" in -> > the body of a message to majordomo at vger.kernel.org +> > the body of a message to majordomo@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > diff --git a/a/content_digest b/N1/content_digest index 07dfb86..4e4e1ea 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,14 +1,19 @@ "ref\0CAHStOZ7m+8xSX=k5k-LwmgZy6Ja4MFwsVjMy-FeoG=2c0rpm2g@mail.gmail.com\0" "ref\01524341993.2601.131.camel@baylibre.com\0" "ref\0CAHStOZ6-jV9gAvJPfk+JKanoNWmWnYykN-u3HwpY9bgoJb1myQ@mail.gmail.com\0" - "From\0jbrunet@baylibre.com (Jerome Brunet)\0" - "Subject\0[PATCH] clk: meson: add the video decoder clocks\0" + "From\0Jerome Brunet <jbrunet@baylibre.com>\0" + "Subject\0Re: [PATCH] clk: meson: add the video decoder clocks\0" "Date\0Mon, 23 Apr 2018 10:52:22 +0200\0" - "To\0linus-amlogic@lists.infradead.org\0" + "To\0Maxime Jourdan <maxi.jourdan@wanadoo.fr>\0" + "Cc\0Neil <narmstrong@baylibre.com>" + Kevin Hilman <khilman@baylibre.com> + Mike Turquette <mturquette@baylibre.com> + linux-amlogic <linux-amlogic@lists.infradead.org> + " linux-clk <linux-clk@vger.kernel.org>\0" "\00:1\0" "b\0" "On Sun, 2018-04-22 at 09:43 +0200, Maxime Jourdan wrote:\n" - "> Hi Neil, J?rome,\n" + "> Hi Neil, J\303\251rome,\n" "\n" "Beware, replies should also be plain text. Some mailing list will block your\n" "mail if it is HTML.\n" @@ -18,7 +23,7 @@ "> \n" "> Thanks for the answers, I'll resubmit with proper formatting.\n" "> \n" - "> @J?rome: very valid points. The usage of the clk will indeed be through set_clk_rate on the leaf clock within the driver, so I don't need to expose the mux. If I want the mux automatically selected to provide the nearest target clock, should I keep CLK_SET_RATE_NO_REPARENT ?\n" + "> @J\303\251rome: very valid points. The usage of the clk will indeed be through set_clk_rate on the leaf clock within the driver, so I don't need to expose the mux. If I want the mux automatically selected to provide the nearest target clock, should I keep CLK_SET_RATE_NO_REPARENT ?\n" "> \n" "\n" "Nope, CLK_SET_RATE_NO_REPARENT tells the clock framework to *keep* the same\n" @@ -267,9 +272,9 @@ "> > \n" "> > --\n" "> > To unsubscribe from this list: send the line \"unsubscribe linux-clk\" in\n" - "> > the body of a message to majordomo at vger.kernel.org\n" + "> > the body of a message to majordomo@vger.kernel.org\n" "> > More majordomo info at http://vger.kernel.org/majordomo-info.html\n" "> \n" > -243b9aa362f2e99babbf91ea6437736d6f1021e8e32e370c119927b513f67069 +25fa835954d78c039b9b6202e7c099f2bd3f028c9241e55cd22b0c44e3f6b8b7
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.