All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <5194AD63.9020804@imgtec.com>

diff --git a/a/1.txt b/N1/1.txt
index 4b1d272..f6dfe10 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -18,7 +18,7 @@ On 15/05/13 23:31, Stephen Boyd wrote:
 > 
 > Can you please Cc the devicetree mailing list when proposing new bindings?
 
-Erm, I think it was on Cc (devicetree-discuss at lists.ozlabs.org yeh?)
+Erm, I think it was on Cc (devicetree-discuss@lists.ozlabs.org yeh?)
 
 > Your patchset brings up a question I've had which is if we should be
 > putting the bits and register width information in devicetree at all. On
diff --git a/a/content_digest b/N1/content_digest
index 973b929..2bf827f 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,9 +1,16 @@
  "ref\01368198127-1295-1-git-send-email-james.hogan@imgtec.com\0"
  "ref\051940CAF.6010808@codeaurora.org\0"
- "From\0james.hogan@imgtec.com (James Hogan)\0"
- "Subject\0[PATCH RFC 0/2] clk: add metag specific gate/mux clocks\0"
+ "From\0James Hogan <james.hogan@imgtec.com>\0"
+ "Subject\0Re: [PATCH RFC 0/2] clk: add metag specific gate/mux clocks\0"
  "Date\0Thu, 16 May 2013 10:56:51 +0100\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Stephen Boyd <sboyd@codeaurora.org>\0"
+ "Cc\0Mike Turquette <mturquette@linaro.org>"
+  linux-arm-kernel@lists.infradead.org
+  linux-kernel@vger.kernel.org
+  Arnd Bergmann <arnd@arndb.de>
+  devicetree-discuss@lists.ozlabs.org <devicetree-discuss@lists.ozlabs.org>
+  Rob Herring <rob.herring@calxeda.com>
+ " Grant Likely <grant.likely@linaro.org>\0"
  "\00:1\0"
  "b\0"
  "On 15/05/13 23:31, Stephen Boyd wrote:\n"
@@ -26,7 +33,7 @@
  "> \n"
  "> Can you please Cc the devicetree mailing list when proposing new bindings?\n"
  "\n"
- "Erm, I think it was on Cc (devicetree-discuss at lists.ozlabs.org yeh?)\n"
+ "Erm, I think it was on Cc (devicetree-discuss@lists.ozlabs.org yeh?)\n"
  "\n"
  "> Your patchset brings up a question I've had which is if we should be\n"
  "> putting the bits and register width information in devicetree at all. On\n"
@@ -54,4 +61,4 @@
  "Cheers\n"
  James
 
-7f57c935320a3b3437beea01689de6893d1ca803e8caf9b30eb447adc98ee70e
+e2f7955e6f0105ba9bb02f97eb7fcf53f7f3fe4487cf2a127aac1addfa5c81d9

diff --git a/a/1.txt b/N2/1.txt
index 4b1d272..f6dfe10 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -18,7 +18,7 @@ On 15/05/13 23:31, Stephen Boyd wrote:
 > 
 > Can you please Cc the devicetree mailing list when proposing new bindings?
 
-Erm, I think it was on Cc (devicetree-discuss at lists.ozlabs.org yeh?)
+Erm, I think it was on Cc (devicetree-discuss@lists.ozlabs.org yeh?)
 
 > Your patchset brings up a question I've had which is if we should be
 > putting the bits and register width information in devicetree at all. On
diff --git a/a/content_digest b/N2/content_digest
index 973b929..a4b2635 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -1,9 +1,16 @@
  "ref\01368198127-1295-1-git-send-email-james.hogan@imgtec.com\0"
  "ref\051940CAF.6010808@codeaurora.org\0"
- "From\0james.hogan@imgtec.com (James Hogan)\0"
- "Subject\0[PATCH RFC 0/2] clk: add metag specific gate/mux clocks\0"
+ "From\0James Hogan <james.hogan@imgtec.com>\0"
+ "Subject\0Re: [PATCH RFC 0/2] clk: add metag specific gate/mux clocks\0"
  "Date\0Thu, 16 May 2013 10:56:51 +0100\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Stephen Boyd <sboyd@codeaurora.org>\0"
+ "Cc\0Mike Turquette <mturquette@linaro.org>"
+  <linux-arm-kernel@lists.infradead.org>
+  <linux-kernel@vger.kernel.org>
+  Arnd Bergmann <arnd@arndb.de>
+  devicetree-discuss@lists.ozlabs.org <devicetree-discuss@lists.ozlabs.org>
+  Rob Herring <rob.herring@calxeda.com>
+ " Grant Likely <grant.likely@linaro.org>\0"
  "\00:1\0"
  "b\0"
  "On 15/05/13 23:31, Stephen Boyd wrote:\n"
@@ -26,7 +33,7 @@
  "> \n"
  "> Can you please Cc the devicetree mailing list when proposing new bindings?\n"
  "\n"
- "Erm, I think it was on Cc (devicetree-discuss at lists.ozlabs.org yeh?)\n"
+ "Erm, I think it was on Cc (devicetree-discuss@lists.ozlabs.org yeh?)\n"
  "\n"
  "> Your patchset brings up a question I've had which is if we should be\n"
  "> putting the bits and register width information in devicetree at all. On\n"
@@ -54,4 +61,4 @@
  "Cheers\n"
  James
 
-7f57c935320a3b3437beea01689de6893d1ca803e8caf9b30eb447adc98ee70e
+50b8a8f019c283be3c5269e5a8208f8feffe031d60f4b9d53a043b1456402c5f

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.