All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20120419064308.GH3852@pengutronix.de>

diff --git a/a/1.txt b/N1/1.txt
index 3985fce..464aa97 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,11 +1,11 @@
 On Wed, Apr 18, 2012 at 11:18:55PM -0500, Rob Lee wrote:
 > >>> If I called imx_cpuidle_init directly from imx5 or imx6q init
 > >>> routines, it would be getting called before the coreinit_call of core
-> >>> cpuidle causing a failure. ?There were various other directions to
+> >>> cpuidle causing a failure.  There were various other directions to
 > >>> take and all seemed less desirable than this one.
 > >>>
 > >>> One alternative would be to add a function to return the pointer to
-> >>> the cpuidle driver object based on the machine type. ?Functionality
+> >>> the cpuidle driver object based on the machine type.  Functionality
 > >>> exists to identify imx5 as a machine type but not imx6q, so I couldn't
 > >>> use that machine based method without adding that extra code.
 > >>>
@@ -16,7 +16,7 @@ On Wed, Apr 18, 2012 at 11:18:55PM -0500, Rob Lee wrote:
 > >> also don't have to make imx5_idle global.
 > >
 > > That solution is currently available for imx5 but for imx6q it implies
-> > adding the cpu type support for imx6q. ?Are you ok with that?
+> > adding the cpu type support for imx6q.  Are you ok with that?
 > 
 > Sascha or Shawn, any further comments on my question?
 
diff --git a/a/content_digest b/N1/content_digest
index e99661c..9292dd7 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -5,20 +5,28 @@
  "ref\020120417174213.GD3852@pengutronix.de\0"
  "ref\0CAMXH7KFYA24sPUcwgKfwVLNPA0jWQ-QG02y+SfPNnAqdiv0+gg@mail.gmail.com\0"
  "ref\0CAMXH7KGgSmvfqUTC1bufBz0QXbt01dHsPo1cbRA9jLj9mGmfjg@mail.gmail.com\0"
- "From\0s.hauer@pengutronix.de (Sascha Hauer)\0"
- "Subject\0[PATCH 1/3] ARM: imx: Add common imx cpuidle init functionality.\0"
+ "From\0Sascha Hauer <s.hauer@pengutronix.de>\0"
+ "Subject\0Re: [PATCH 1/3] ARM: imx: Add common imx cpuidle init functionality.\0"
  "Date\0Thu, 19 Apr 2012 08:43:08 +0200\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Rob Lee <rob.lee@linaro.org>\0"
+ "Cc\0Amit Kucheria <amit.kucheria@linaro.org>"
+  shawn.guo@linaro.org
+  kernel@pengutronix.de
+  linaro-dev@lists.linaro.org
+  patches@linaro.org
+  daniel.lezcano@linaro.org
+  linux-kernel@vger.kernel.org
+ " linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On Wed, Apr 18, 2012 at 11:18:55PM -0500, Rob Lee wrote:\n"
  "> >>> If I called imx_cpuidle_init directly from imx5 or imx6q init\n"
  "> >>> routines, it would be getting called before the coreinit_call of core\n"
- "> >>> cpuidle causing a failure. ?There were various other directions to\n"
+ "> >>> cpuidle causing a failure. \302\240There were various other directions to\n"
  "> >>> take and all seemed less desirable than this one.\n"
  "> >>>\n"
  "> >>> One alternative would be to add a function to return the pointer to\n"
- "> >>> the cpuidle driver object based on the machine type. ?Functionality\n"
+ "> >>> the cpuidle driver object based on the machine type. \302\240Functionality\n"
  "> >>> exists to identify imx5 as a machine type but not imx6q, so I couldn't\n"
  "> >>> use that machine based method without adding that extra code.\n"
  "> >>>\n"
@@ -29,7 +37,7 @@
  "> >> also don't have to make imx5_idle global.\n"
  "> >\n"
  "> > That solution is currently available for imx5 but for imx6q it implies\n"
- "> > adding the cpu type support for imx6q. ?Are you ok with that?\n"
+ "> > adding the cpu type support for imx6q. \302\240Are you ok with that?\n"
  "> \n"
  "> Sascha or Shawn, any further comments on my question?\n"
  "\n"
@@ -45,4 +53,4 @@
  "Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |\n"
  Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
 
-b7273c516625dcf22e7f8a5ba960c1801c986fe553d4c033386bd6126a4cf321
+7660007f1f07b3d53390d23e71043f87e453149bf5262d0f20d3181cfd2b44ed

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.