All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <4E00EB41.9080606@firmworks.com>

diff --git a/a/content_digest b/N1/content_digest
index d7248f1..bc35a29 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -5,10 +5,19 @@
  "ref\020110621135558.GB9228@S2101-09.ap.freescale.net\0"
  "ref\04E00E3D2.6050602@firmworks.com\0"
  "ref\0BANLkTiny9xDwiUww9Ys+jQZ0SHdQATABUA@mail.gmail.com\0"
- "From\0wmb@firmworks.com (Mitch Bradley)\0"
- "Subject\0[PATCH 1/3] serial/imx: add device tree support\0"
+ "From\0Mitch Bradley <wmb@firmworks.com>\0"
+ "Subject\0Re: [PATCH 1/3] serial/imx: add device tree support\0"
  "Date\0Tue, 21 Jun 2011 09:04:33 -1000\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Grant Likely <grant.likely@secretlab.ca>\0"
+ "Cc\0Shawn Guo <shawn.guo@freescale.com>"
+  patches@linaro.org
+  netdev@vger.kernel.org
+  devicetree-discuss@lists.ozlabs.org
+  Jason Liu <jason.hui@linaro.org>
+  linux-kernel@vger.kernel.org
+  Jeremy Kerr <jeremy.kerr@canonical.com>
+  Sascha Hauer <s.hauer@pengutronix.de>
+ " linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On 6/21/2011 8:42 AM, Grant Likely wrote:\n"
@@ -48,4 +57,4 @@
  ">\n"
  >
 
-22e4cac0c4a85197fbe413fcf8528d82845e39e5d3571014d7ac03b03fc1d282
+8f41d6fc1341ed0d5007a1071d30775ef4a9575134c110f0d87bb379e88e507e

diff --git a/a/1.txt b/N2/1.txt
index c0439e7..ffc40b0 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -1,5 +1,5 @@
 On 6/21/2011 8:42 AM, Grant Likely wrote:
-> On Tue, Jun 21, 2011 at 12:32 PM, Mitch Bradley<wmb@firmworks.com>  wrote:
+> On Tue, Jun 21, 2011 at 12:32 PM, Mitch Bradley<wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>  wrote:
 >> I wonder if it makes sense to create a new device node "/linux-devices" to express a desired mapping from device nodes to /dev entries?  The properties could be the names of device special files and the values the corresponding node phandles.
 >
 > I've been trying /really/ hard to avoid doing something like that
diff --git a/a/content_digest b/N2/content_digest
index d7248f1..e53af8f 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -5,14 +5,23 @@
  "ref\020110621135558.GB9228@S2101-09.ap.freescale.net\0"
  "ref\04E00E3D2.6050602@firmworks.com\0"
  "ref\0BANLkTiny9xDwiUww9Ys+jQZ0SHdQATABUA@mail.gmail.com\0"
- "From\0wmb@firmworks.com (Mitch Bradley)\0"
- "Subject\0[PATCH 1/3] serial/imx: add device tree support\0"
+ "ref\0BANLkTiny9xDwiUww9Ys+jQZ0SHdQATABUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org\0"
+ "From\0Mitch Bradley <wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>\0"
+ "Subject\0Re: [PATCH 1/3] serial/imx: add device tree support\0"
  "Date\0Tue, 21 Jun 2011 09:04:33 -1000\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>\0"
+ "Cc\0patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
+  netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
+  devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
+  Jason Liu <jason.hui-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
+  linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
+  linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
+  Jeremy Kerr <jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
+ " Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>\0"
  "\00:1\0"
  "b\0"
  "On 6/21/2011 8:42 AM, Grant Likely wrote:\n"
- "> On Tue, Jun 21, 2011 at 12:32 PM, Mitch Bradley<wmb@firmworks.com>  wrote:\n"
+ "> On Tue, Jun 21, 2011 at 12:32 PM, Mitch Bradley<wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>  wrote:\n"
  ">> I wonder if it makes sense to create a new device node \"/linux-devices\" to express a desired mapping from device nodes to /dev entries?  The properties could be the names of device special files and the values the corresponding node phandles.\n"
  ">\n"
  "> I've been trying /really/ hard to avoid doing something like that\n"
@@ -48,4 +57,4 @@
  ">\n"
  >
 
-22e4cac0c4a85197fbe413fcf8528d82845e39e5d3571014d7ac03b03fc1d282
+05f7dc88050de1aea02275f5eb48c6a27845941db3f24239e074491bca5e459b

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.