All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <53087A0F.6010302@linaro.org>

diff --git a/a/1.txt b/N1/1.txt
index 1329cfe..29b65f0 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -8,7 +8,7 @@ On 2014-2-21 20:37, Sudeep Holla wrote:
 >>
 >> Thanks for your comments, please refer to the replies below. :)
 >>
->> On 2014年02月19日 22:33, Sudeep Holla wrote:
+>> On 2014?02?19? 22:33, Sudeep Holla wrote:
 >>> Hi Hanjun,
 >>>
 >>> On 18/02/14 16:23, Hanjun Guo wrote:
@@ -73,7 +73,7 @@ On 2014-2-21 20:37, Sudeep Holla wrote:
 I agree.
 
 > 
-> The GIC ID is referred as the local GIC’s hardware ID in ACPIv5.0.
+> The GIC ID is referred as the local GIC?s hardware ID in ACPIv5.0.
 > IIUC, since GICC is per-cpu entry, it has to GIC CPU interface ID.
 > 
 > Now how does it differ from MPIDR ? e.g. ARM TC2(multi cluster system)
diff --git a/a/content_digest b/N1/content_digest
index b73a3d8..6e0cec6 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,19 +3,10 @@
  "ref\05304C0C4.3080601@arm.com\0"
  "ref\053057DA9.3010307@linaro.org\0"
  "ref\05307487F.6000308@arm.com\0"
- "From\0Hanjun Guo <hanjun.guo@linaro.org>\0"
- "Subject\0Re: [PATCH v5 3/5] ACPI / processor: Introduce map_gic_id() to get apic id from MADT or _MAT method\0"
+ "From\0hanjun.guo@linaro.org (Hanjun Guo)\0"
+ "Subject\0[PATCH v5 3/5] ACPI / processor: Introduce map_gic_id() to get apic id from MADT or _MAT method\0"
  "Date\0Sat, 22 Feb 2014 18:21:03 +0800\0"
- "To\0Sudeep Holla <Sudeep.Holla@arm.com>\0"
- "Cc\0Rafael J. Wysocki <rjw@rjwysocki.net>"
-  Lan Tianyu <tianyu.lan@intel.com>
-  patches@linaro.org <patches@linaro.org>
-  linaro-acpi@lists.linaro.org <linaro-acpi@lists.linaro.org>
-  linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
-  linux-acpi@vger.kernel.org <linux-acpi@vger.kernel.org>
-  Joe Perches <joe@perches.com>
-  linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>
- " Marc Zyngier <Marc.Zyngier@arm.com>\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On 2014-2-21 20:37, Sudeep Holla wrote:\n"
@@ -28,7 +19,7 @@
  ">>\n"
  ">> Thanks for your comments, please refer to the replies below. :)\n"
  ">>\n"
- ">> On 2014\345\271\26402\346\234\21019\346\227\245 22:33, Sudeep Holla wrote:\n"
+ ">> On 2014?02?19? 22:33, Sudeep Holla wrote:\n"
  ">>> Hi Hanjun,\n"
  ">>>\n"
  ">>> On 18/02/14 16:23, Hanjun Guo wrote:\n"
@@ -93,7 +84,7 @@
  "I agree.\n"
  "\n"
  "> \n"
- "> The GIC ID is referred as the local GIC\342\200\231s hardware ID in ACPIv5.0.\n"
+ "> The GIC ID is referred as the local GIC?s hardware ID in ACPIv5.0.\n"
  "> IIUC, since GICC is per-cpu entry, it has to GIC CPU interface ID.\n"
  "> \n"
  "> Now how does it differ from MPIDR ? e.g. ARM TC2(multi cluster system)\n"
@@ -176,4 +167,4 @@
  "Thanks\n"
  Hanjun
 
-e56544677f3d784947d2bb64a0cf3f122ea23181af95f6a5364ab4ca1aa49228
+47858a5cca3cdfa04dd86d0f7a5cbd0af9d239a745dd8ba3d5d07f6cbda97e72

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.