All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20180404220750.0436bbe1@gmail.com>

diff --git a/a/1.txt b/N1/1.txt
index 67b61d7..2d96528 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -31,8 +31,3 @@ I guess that would be a separate driver, that would manage the nmem devices
 and there would be a way to relate the pmem and nmems. Oliver?
 
 Balbir Singh.
-
-_______________________________________________
-Linux-nvdimm mailing list
-Linux-nvdimm@lists.01.org
-https://lists.01.org/mailman/listinfo/linux-nvdimm
diff --git a/a/content_digest b/N1/content_digest
index db2cd8e..61659b4 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -5,7 +5,8 @@
  "Subject\0Re: [RESEND v2 3/4] doc/devicetree: Persistent memory region bindings\0"
  "Date\0Wed, 4 Apr 2018 22:07:50 +1000\0"
  "To\0Dan Williams <dan.j.williams@intel.com>\0"
- "Cc\0Device Tree <devicetree@vger.kernel.org>"
+ "Cc\0Oliver O'Halloran <oohall@gmail.com>"
+  Device Tree <devicetree@vger.kernel.org>
   linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
  " linux-nvdimm <linux-nvdimm@lists.01.org>\0"
  "\00:1\0"
@@ -42,11 +43,6 @@
  "I guess that would be a separate driver, that would manage the nmem devices\n"
  "and there would be a way to relate the pmem and nmems. Oliver?\n"
  "\n"
- "Balbir Singh.\n"
- "\n"
- "_______________________________________________\n"
- "Linux-nvdimm mailing list\n"
- "Linux-nvdimm@lists.01.org\n"
- https://lists.01.org/mailman/listinfo/linux-nvdimm
+ Balbir Singh.
 
-5eec0e9f86dcb167013b199d03dc7aa06e9e021331ed8c0dd4336138f9575bd4
+a880d80cdcb418df72e6d86571ab59ab514e779472bb572b8a19c4b62944f0ec

diff --git a/a/1.txt b/N2/1.txt
index 67b61d7..f41299b 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -1,11 +1,11 @@
 On Tue, 3 Apr 2018 10:37:51 -0700
-Dan Williams <dan.j.williams@intel.com> wrote:
+Dan Williams <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:
 
-> On Tue, Apr 3, 2018 at 7:24 AM, Oliver O'Halloran <oohall@gmail.com> wrote:
+> On Tue, Apr 3, 2018 at 7:24 AM, Oliver O'Halloran <oohall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
 > > Add device-tree binding documentation for the nvdimm region driver.
 > >
-> > Cc: devicetree@vger.kernel.org
-> > Signed-off-by: Oliver O'Halloran <oohall@gmail.com>
+> > Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
+> > Signed-off-by: Oliver O'Halloran <oohall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
 > > ---
 > > v2: Changed name from nvdimm-region to pmem-region.
 > >     Cleaned up the example binding and fixed the overlapping regions.
@@ -31,8 +31,3 @@ I guess that would be a separate driver, that would manage the nmem devices
 and there would be a way to relate the pmem and nmems. Oliver?
 
 Balbir Singh.
-
-_______________________________________________
-Linux-nvdimm mailing list
-Linux-nvdimm@lists.01.org
-https://lists.01.org/mailman/listinfo/linux-nvdimm
diff --git a/a/content_digest b/N2/content_digest
index db2cd8e..29b5540 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -1,23 +1,24 @@
  "ref\020180403142415.30083-1-oohall@gmail.com\0"
  "ref\020180403142415.30083-3-oohall@gmail.com\0"
  "ref\0CAPcyv4jW5H8A96MFD7-UazNSZq-t1_NfrChNB3p9=somdBpsNw@mail.gmail.com\0"
- "From\0Balbir Singh <bsingharora@gmail.com>\0"
+ "ref\0CAPcyv4jW5H8A96MFD7-UazNSZq-t1_NfrChNB3p9=somdBpsNw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org\0"
+ "From\0Balbir Singh <bsingharora-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>\0"
  "Subject\0Re: [RESEND v2 3/4] doc/devicetree: Persistent memory region bindings\0"
  "Date\0Wed, 4 Apr 2018 22:07:50 +1000\0"
- "To\0Dan Williams <dan.j.williams@intel.com>\0"
- "Cc\0Device Tree <devicetree@vger.kernel.org>"
-  linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
- " linux-nvdimm <linux-nvdimm@lists.01.org>\0"
+ "To\0Dan Williams <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>\0"
+ "Cc\0Device Tree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>"
+  linuxppc-dev <linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
+ " linux-nvdimm <linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org>\0"
  "\00:1\0"
  "b\0"
  "On Tue, 3 Apr 2018 10:37:51 -0700\n"
- "Dan Williams <dan.j.williams@intel.com> wrote:\n"
+ "Dan Williams <dan.j.williams-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:\n"
  "\n"
- "> On Tue, Apr 3, 2018 at 7:24 AM, Oliver O'Halloran <oohall@gmail.com> wrote:\n"
+ "> On Tue, Apr 3, 2018 at 7:24 AM, Oliver O'Halloran <oohall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:\n"
  "> > Add device-tree binding documentation for the nvdimm region driver.\n"
  "> >\n"
- "> > Cc: devicetree@vger.kernel.org\n"
- "> > Signed-off-by: Oliver O'Halloran <oohall@gmail.com>\n"
+ "> > Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n"
+ "> > Signed-off-by: Oliver O'Halloran <oohall-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>\n"
  "> > ---\n"
  "> > v2: Changed name from nvdimm-region to pmem-region.\n"
  "> >     Cleaned up the example binding and fixed the overlapping regions.\n"
@@ -42,11 +43,6 @@
  "I guess that would be a separate driver, that would manage the nmem devices\n"
  "and there would be a way to relate the pmem and nmems. Oliver?\n"
  "\n"
- "Balbir Singh.\n"
- "\n"
- "_______________________________________________\n"
- "Linux-nvdimm mailing list\n"
- "Linux-nvdimm@lists.01.org\n"
- https://lists.01.org/mailman/listinfo/linux-nvdimm
+ Balbir Singh.
 
-5eec0e9f86dcb167013b199d03dc7aa06e9e021331ed8c0dd4336138f9575bd4
+f0d22907c2b0e44bf2cd9b61ac77bb14c969e4c53b9ded117628c5060ba48c17

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.