diff for duplicates of <20130802220935.6450.38975@quantum> diff --git a/a/1.txt b/N1/1.txt index 52fed82..993ef44 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,64 +1,43 @@ Quoting Nicolas Pitre (2013-07-18 10:47:22) > On Thu, 18 Jul 2013, Russell King - ARM Linux wrote: -> = - +> > > 1. clk_get() and clk_put() are NOT part of the common clock API. -> > They're separate - they're part of the clk API, and the infrastructu= -re +> > They're separate - they're part of the clk API, and the infrastructure > > behind that is clkdev, which is a separately owned thing (by me.) -> > = - +> > > > 2. The "contract" of the clk API is defined by the clk API, not by some > > random implementation like the common clock API. The clk API is > > maintained by myself, and is described in include/linux/clk.h -> > = - +> > > > 3. clk_prepare() and clk_unprepare() are functions MUST only be called > > from contexts where sleeping is permitted. These functions MAY sleep > > for whatever reason they require to, and as long as they require to. > > (This is the whole reason these two functions were created in the > > first place.) -> > = - +> > > > 4. clk_enable() and clk_disable() MAY be called from any context, but -> > MUST never sleep. If you need to talk over a non-atomic bus for the= -se, +> > MUST never sleep. If you need to talk over a non-atomic bus for these, > > then these functions should be no-ops, and the code which does that > > must be executed from the clk_prepare()/clk_unprepare() operations. -> = - -> Could the above be included in some form in Documentation/clk.txt (this = - -> is likely one of the first location people look for information) and = - +> +> Could the above be included in some form in Documentation/clk.txt (this +> is likely one of the first location people look for information) and > elsewhere if appropriate please? -> = - -> A *lot* of people are confused by the prepare-enable-disable-unprepare = - -> sequence and when I try to find some rational for the prepare/enable = - -> split I can only direct them to mail archive posts since this is nowhere = - +> +> A *lot* of people are confused by the prepare-enable-disable-unprepare +> sequence and when I try to find some rational for the prepare/enable +> split I can only direct them to mail archive posts since this is nowhere > to be found in the kernel. -> = - -> The comments in include/linux/clk.h, while correct, are very terse and = - +> +> The comments in include/linux/clk.h, while correct, are very terse and > don't provide any insight to the reason why there is a split in the API. -> = - -> The content of Documentation/clk.txt does refer to prepare and enable = - -> (and their counterparts) but again doesn't provide any clue about the = - +> +> The content of Documentation/clk.txt does refer to prepare and enable +> (and their counterparts) but again doesn't provide any clue about the > reason for their existence. -> = - -> Since there've been several good posts with usage example now buried = - -> into list archives, I think this would go a long way helping people get = - +> +> Since there've been several good posts with usage example now buried +> into list archives, I think this would go a long way helping people get > it right if those were part of the kernel documentation as well. I'll update Documentation/clk.txt with more verbosity. The document was @@ -69,8 +48,6 @@ the document should probably be generalized a bit more. Regards, Mike -> = - -> = - +> +> > Nicolas diff --git a/a/content_digest b/N1/content_digest index 3c44bed..22c2ad9 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,88 +4,52 @@ "ref\020130718070402.GO7080@book.gsilab.sittig.org\0" "ref\020130718091735.GW24642@n2100.arm.linux.org.uk\0" "ref\0alpine.LFD.2.03.1307181330520.14924@syhkavp.arg\0" - "From\0Mike Turquette <mturquette@linaro.org>\0" - "Subject\0Re: [PATCH v1 05/24] clk: wrap I/O access for improved portability\0" + "From\0mturquette@linaro.org (Mike Turquette)\0" + "Subject\0[PATCH v1 05/24] clk: wrap I/O access for improved portability\0" "Date\0Fri, 02 Aug 2013 15:09:35 -0700\0" - "To\0Nicolas Pitre <nicolas.pitre@linaro.org>" - " Russell King - ARM Linux <linux@arm.linux.org.uk>\0" - "Cc\0Detlev Zundel <dzu@denx.de>" - Wolfram Sang <wsa@the-dreams.de> - devicetree-discuss@lists.ozlabs.org - Greg Kroah-Hartman <gregkh@linuxfoundation.org> - Gerhard Sittig <gsi@denx.de> - linuxppc-dev@lists.ozlabs.org - Rob Herring <rob.herring@calxeda.com> - Mark Brown <broonie@kernel.org> - Marc Kleine-Budde <mkl@pengutronix.de> - Wolfgang Grandegger <wg@grandegger.com> - David Woodhouse <dwmw2@infradead.org> - Sascha Hauer <s.hauer@pengutronix.de> - linux-arm-kernel@lists.infradead.org - " Mauro Carvalho Chehab <m.chehab@samsung.com>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "Quoting Nicolas Pitre (2013-07-18 10:47:22)\n" "> On Thu, 18 Jul 2013, Russell King - ARM Linux wrote:\n" - "> =\n" - "\n" + "> \n" "> > 1. clk_get() and clk_put() are NOT part of the common clock API.\n" - "> > They're separate - they're part of the clk API, and the infrastructu=\n" - "re\n" + "> > They're separate - they're part of the clk API, and the infrastructure\n" "> > behind that is clkdev, which is a separately owned thing (by me.)\n" - "> > =\n" - "\n" + "> > \n" "> > 2. The \"contract\" of the clk API is defined by the clk API, not by some\n" "> > random implementation like the common clock API. The clk API is\n" "> > maintained by myself, and is described in include/linux/clk.h\n" - "> > =\n" - "\n" + "> > \n" "> > 3. clk_prepare() and clk_unprepare() are functions MUST only be called\n" "> > from contexts where sleeping is permitted. These functions MAY sleep\n" "> > for whatever reason they require to, and as long as they require to.\n" "> > (This is the whole reason these two functions were created in the\n" "> > first place.)\n" - "> > =\n" - "\n" + "> > \n" "> > 4. clk_enable() and clk_disable() MAY be called from any context, but\n" - "> > MUST never sleep. If you need to talk over a non-atomic bus for the=\n" - "se,\n" + "> > MUST never sleep. If you need to talk over a non-atomic bus for these,\n" "> > then these functions should be no-ops, and the code which does that\n" "> > must be executed from the clk_prepare()/clk_unprepare() operations.\n" - "> =\n" - "\n" - "> Could the above be included in some form in Documentation/clk.txt (this =\n" - "\n" - "> is likely one of the first location people look for information) and =\n" - "\n" + "> \n" + "> Could the above be included in some form in Documentation/clk.txt (this \n" + "> is likely one of the first location people look for information) and \n" "> elsewhere if appropriate please?\n" - "> =\n" - "\n" - "> A *lot* of people are confused by the prepare-enable-disable-unprepare =\n" - "\n" - "> sequence and when I try to find some rational for the prepare/enable =\n" - "\n" - "> split I can only direct them to mail archive posts since this is nowhere =\n" - "\n" + "> \n" + "> A *lot* of people are confused by the prepare-enable-disable-unprepare \n" + "> sequence and when I try to find some rational for the prepare/enable \n" + "> split I can only direct them to mail archive posts since this is nowhere \n" "> to be found in the kernel.\n" - "> =\n" - "\n" - "> The comments in include/linux/clk.h, while correct, are very terse and =\n" - "\n" + "> \n" + "> The comments in include/linux/clk.h, while correct, are very terse and \n" "> don't provide any insight to the reason why there is a split in the API.\n" - "> =\n" - "\n" - "> The content of Documentation/clk.txt does refer to prepare and enable =\n" - "\n" - "> (and their counterparts) but again doesn't provide any clue about the =\n" - "\n" + "> \n" + "> The content of Documentation/clk.txt does refer to prepare and enable \n" + "> (and their counterparts) but again doesn't provide any clue about the \n" "> reason for their existence.\n" - "> =\n" - "\n" - "> Since there've been several good posts with usage example now buried =\n" - "\n" - "> into list archives, I think this would go a long way helping people get =\n" - "\n" + "> \n" + "> Since there've been several good posts with usage example now buried \n" + "> into list archives, I think this would go a long way helping people get \n" "> it right if those were part of the kernel documentation as well.\n" "\n" "I'll update Documentation/clk.txt with more verbosity. The document was\n" @@ -96,10 +60,8 @@ "Regards,\n" "Mike\n" "\n" - "> =\n" - "\n" - "> =\n" - "\n" + "> \n" + "> \n" > Nicolas -9ca5ccb96a1a8b48591b0fcb1fa2c6fe2ee79845f194fc8945e54c74a9f0f27a +d2842fff742c072bd6c36ff5d000ac50830f4eab4cad36b8dec1a418bd6dd26c
diff --git a/a/1.txt b/N2/1.txt index 52fed82..993ef44 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,64 +1,43 @@ Quoting Nicolas Pitre (2013-07-18 10:47:22) > On Thu, 18 Jul 2013, Russell King - ARM Linux wrote: -> = - +> > > 1. clk_get() and clk_put() are NOT part of the common clock API. -> > They're separate - they're part of the clk API, and the infrastructu= -re +> > They're separate - they're part of the clk API, and the infrastructure > > behind that is clkdev, which is a separately owned thing (by me.) -> > = - +> > > > 2. The "contract" of the clk API is defined by the clk API, not by some > > random implementation like the common clock API. The clk API is > > maintained by myself, and is described in include/linux/clk.h -> > = - +> > > > 3. clk_prepare() and clk_unprepare() are functions MUST only be called > > from contexts where sleeping is permitted. These functions MAY sleep > > for whatever reason they require to, and as long as they require to. > > (This is the whole reason these two functions were created in the > > first place.) -> > = - +> > > > 4. clk_enable() and clk_disable() MAY be called from any context, but -> > MUST never sleep. If you need to talk over a non-atomic bus for the= -se, +> > MUST never sleep. If you need to talk over a non-atomic bus for these, > > then these functions should be no-ops, and the code which does that > > must be executed from the clk_prepare()/clk_unprepare() operations. -> = - -> Could the above be included in some form in Documentation/clk.txt (this = - -> is likely one of the first location people look for information) and = - +> +> Could the above be included in some form in Documentation/clk.txt (this +> is likely one of the first location people look for information) and > elsewhere if appropriate please? -> = - -> A *lot* of people are confused by the prepare-enable-disable-unprepare = - -> sequence and when I try to find some rational for the prepare/enable = - -> split I can only direct them to mail archive posts since this is nowhere = - +> +> A *lot* of people are confused by the prepare-enable-disable-unprepare +> sequence and when I try to find some rational for the prepare/enable +> split I can only direct them to mail archive posts since this is nowhere > to be found in the kernel. -> = - -> The comments in include/linux/clk.h, while correct, are very terse and = - +> +> The comments in include/linux/clk.h, while correct, are very terse and > don't provide any insight to the reason why there is a split in the API. -> = - -> The content of Documentation/clk.txt does refer to prepare and enable = - -> (and their counterparts) but again doesn't provide any clue about the = - +> +> The content of Documentation/clk.txt does refer to prepare and enable +> (and their counterparts) but again doesn't provide any clue about the > reason for their existence. -> = - -> Since there've been several good posts with usage example now buried = - -> into list archives, I think this would go a long way helping people get = - +> +> Since there've been several good posts with usage example now buried +> into list archives, I think this would go a long way helping people get > it right if those were part of the kernel documentation as well. I'll update Documentation/clk.txt with more verbosity. The document was @@ -69,8 +48,6 @@ the document should probably be generalized a bit more. Regards, Mike -> = - -> = - +> +> > Nicolas diff --git a/a/content_digest b/N2/content_digest index 3c44bed..844c364 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -27,65 +27,44 @@ "b\0" "Quoting Nicolas Pitre (2013-07-18 10:47:22)\n" "> On Thu, 18 Jul 2013, Russell King - ARM Linux wrote:\n" - "> =\n" - "\n" + "> \n" "> > 1. clk_get() and clk_put() are NOT part of the common clock API.\n" - "> > They're separate - they're part of the clk API, and the infrastructu=\n" - "re\n" + "> > They're separate - they're part of the clk API, and the infrastructure\n" "> > behind that is clkdev, which is a separately owned thing (by me.)\n" - "> > =\n" - "\n" + "> > \n" "> > 2. The \"contract\" of the clk API is defined by the clk API, not by some\n" "> > random implementation like the common clock API. The clk API is\n" "> > maintained by myself, and is described in include/linux/clk.h\n" - "> > =\n" - "\n" + "> > \n" "> > 3. clk_prepare() and clk_unprepare() are functions MUST only be called\n" "> > from contexts where sleeping is permitted. These functions MAY sleep\n" "> > for whatever reason they require to, and as long as they require to.\n" "> > (This is the whole reason these two functions were created in the\n" "> > first place.)\n" - "> > =\n" - "\n" + "> > \n" "> > 4. clk_enable() and clk_disable() MAY be called from any context, but\n" - "> > MUST never sleep. If you need to talk over a non-atomic bus for the=\n" - "se,\n" + "> > MUST never sleep. If you need to talk over a non-atomic bus for these,\n" "> > then these functions should be no-ops, and the code which does that\n" "> > must be executed from the clk_prepare()/clk_unprepare() operations.\n" - "> =\n" - "\n" - "> Could the above be included in some form in Documentation/clk.txt (this =\n" - "\n" - "> is likely one of the first location people look for information) and =\n" - "\n" + "> \n" + "> Could the above be included in some form in Documentation/clk.txt (this \n" + "> is likely one of the first location people look for information) and \n" "> elsewhere if appropriate please?\n" - "> =\n" - "\n" - "> A *lot* of people are confused by the prepare-enable-disable-unprepare =\n" - "\n" - "> sequence and when I try to find some rational for the prepare/enable =\n" - "\n" - "> split I can only direct them to mail archive posts since this is nowhere =\n" - "\n" + "> \n" + "> A *lot* of people are confused by the prepare-enable-disable-unprepare \n" + "> sequence and when I try to find some rational for the prepare/enable \n" + "> split I can only direct them to mail archive posts since this is nowhere \n" "> to be found in the kernel.\n" - "> =\n" - "\n" - "> The comments in include/linux/clk.h, while correct, are very terse and =\n" - "\n" + "> \n" + "> The comments in include/linux/clk.h, while correct, are very terse and \n" "> don't provide any insight to the reason why there is a split in the API.\n" - "> =\n" - "\n" - "> The content of Documentation/clk.txt does refer to prepare and enable =\n" - "\n" - "> (and their counterparts) but again doesn't provide any clue about the =\n" - "\n" + "> \n" + "> The content of Documentation/clk.txt does refer to prepare and enable \n" + "> (and their counterparts) but again doesn't provide any clue about the \n" "> reason for their existence.\n" - "> =\n" - "\n" - "> Since there've been several good posts with usage example now buried =\n" - "\n" - "> into list archives, I think this would go a long way helping people get =\n" - "\n" + "> \n" + "> Since there've been several good posts with usage example now buried \n" + "> into list archives, I think this would go a long way helping people get \n" "> it right if those were part of the kernel documentation as well.\n" "\n" "I'll update Documentation/clk.txt with more verbosity. The document was\n" @@ -96,10 +75,8 @@ "Regards,\n" "Mike\n" "\n" - "> =\n" - "\n" - "> =\n" - "\n" + "> \n" + "> \n" > Nicolas -9ca5ccb96a1a8b48591b0fcb1fa2c6fe2ee79845f194fc8945e54c74a9f0f27a +5e97062b645141b1856cca910e92f83f09d96259dbcb22701f17ad980d4a1db5
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.