diff for duplicates of <20150812164649.31346.9236@quantum> diff --git a/a/1.txt b/N1/1.txt index 1157d4a..70af54a 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -5,30 +5,24 @@ Quoting Felipe Balbi (2015-08-12 08:02:53) > > > > Quoting Russell King - ARM Linux (2015-08-11 12:25:15) > > > >> > > > >> clk_enable/clk_disable _should_ be usable from atomic contexts. -> > > = - +> > > > > > Thanks Russell - above is not true on -RT. -> > = - +> > > > What I'm saying is that it _should_ be true. You _should_ be able to > > call clk_enable()/clk_disable() from atomic contexts. It's been > > documented since forever: -> > = - +> > > > /** -> > * clk_enable - inform the system when the clock source should be runni= -ng. +> > * clk_enable - inform the system when the clock source should be running. > > * @clk: clock source > > * > > * If the clock can not be enabled/disabled, this should return success. > > * > > * May be called from atomic contexts. > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -> > = - +> > > > /** -> > * clk_disable - inform the system when the clock source is no longer r= -equired. +> > * clk_disable - inform the system when the clock source is no longer required. > > * @clk: clock source > > * > > * Inform the system that a clock source is no longer required by @@ -36,11 +30,9 @@ equired. > > * > > * May be called from atomic contexts. > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -> > = - +> > > > If that's not true with CCF, that's a CCF bug, not a usage bug. -> = - +> > in that case, CCF's clock need to be converted to raw_spin_locks, that's > the only way to prevent its locks from being reimplemented as rt > mutexes. @@ -53,8 +45,6 @@ required... Regards, Mike -> = - -> -- = - +> +> -- > balbi diff --git a/a/content_digest b/N1/content_digest index c285b7e..e7b35b6 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -30,30 +30,24 @@ "> > > > Quoting Russell King - ARM Linux (2015-08-11 12:25:15)\n" "> > > >>\n" "> > > >> clk_enable/clk_disable _should_ be usable from atomic contexts.\n" - "> > > =\n" - "\n" + "> > > \n" "> > > Thanks Russell - above is not true on -RT.\n" - "> > =\n" - "\n" + "> > \n" "> > What I'm saying is that it _should_ be true. You _should_ be able to\n" "> > call clk_enable()/clk_disable() from atomic contexts. It's been\n" "> > documented since forever:\n" - "> > =\n" - "\n" + "> > \n" "> > /**\n" - "> > * clk_enable - inform the system when the clock source should be runni=\n" - "ng.\n" + "> > * clk_enable - inform the system when the clock source should be running.\n" "> > * @clk: clock source\n" "> > *\n" "> > * If the clock can not be enabled/disabled, this should return success.\n" "> > *\n" "> > * May be called from atomic contexts.\n" "> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n" - "> > =\n" - "\n" + "> > \n" "> > /**\n" - "> > * clk_disable - inform the system when the clock source is no longer r=\n" - "equired.\n" + "> > * clk_disable - inform the system when the clock source is no longer required.\n" "> > * @clk: clock source\n" "> > *\n" "> > * Inform the system that a clock source is no longer required by\n" @@ -61,11 +55,9 @@ "> > *\n" "> > * May be called from atomic contexts.\n" "> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n" - "> > =\n" - "\n" + "> > \n" "> > If that's not true with CCF, that's a CCF bug, not a usage bug.\n" - "> =\n" - "\n" + "> \n" "> in that case, CCF's clock need to be converted to raw_spin_locks, that's\n" "> the only way to prevent its locks from being reimplemented as rt\n" "> mutexes.\n" @@ -78,10 +70,8 @@ "Regards,\n" "Mike\n" "\n" - "> =\n" - "\n" - "> -- =\n" - "\n" + "> \n" + "> -- \n" > balbi -a16e679482fcfc0a85f3edff942091cbb50a04b2e34d7b81eeb154f1299cbc75 +d2e6525cfcf35f438faa36f2bc9c60ec1b81dd140d6c95388d708db0f0d549ca
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.