All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <1509722197.15520.17.camel@perches.com>

diff --git a/a/1.txt b/N1/1.txt
index eda27ee..560df5d 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,20 +1,18 @@
-On Fri, 2017-11-03 at 13:55 +0100, Christoph Hellwig wrote:
-> On Fri, Nov 03, 2017 at 11:02:50AM +0100, Javier Gonz=E1lez wrote:
-> > Signed-off-by: Javier Gonz=E1lez <javier@cnexlabs.com>
+On Fri, 2017-11-03@13:55 +0100, Christoph Hellwig wrote:
+> On Fri, Nov 03, 2017@11:02:50AM +0100, Javier Gonz?lez wrote:
+> > Signed-off-by: Javier Gonz?lez <javier at cnexlabs.com>
 []
 > > diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
 []
-> > @@ -2108,7 +2108,7 @@ static ssize_t eui_show(struct device *dev, struc=
-t device_attribute *attr,
+> > @@ -2108,7 +2108,7 @@ static ssize_t eui_show(struct device *dev, struct device_attribute *attr,
 > >  								char *buf)
 > >  {
-> >  	struct nvme_ns *ns =3D nvme_get_ns_from_dev(dev);
+> >  	struct nvme_ns *ns = nvme_get_ns_from_dev(dev);
 > > -	return sprintf(buf, "%8phd\n", ns->eui);
 > > +	return sprintf(buf, "%8phD\n", ns->eui);
 > >  }
 > >  static DEVICE_ATTR(eui, S_IRUGO, eui_show, NULL);
-> =
-
+> 
 > This looks correct.  I wonder what the old code printed - does someone
 > have a device with an EUI-64 at hand to quickly cross check what we
 > did before?
@@ -32,10 +30,3 @@ Perhaps this should just become
 	%8ph
 
 without D
-
-
-
-_______________________________________________
-Linux-nvme mailing list
-Linux-nvme@lists.infradead.org
-http://lists.infradead.org/mailman/listinfo/linux-nvme
diff --git a/a/content_digest b/N1/content_digest
index 2b849d0..2753d26 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,36 +1,26 @@
  "ref\01509703370-20379-1-git-send-email-javier@cnexlabs.com\0"
  "ref\01509703370-20379-4-git-send-email-javier@cnexlabs.com\0"
  "ref\020171103125516.GC25186@lst.de\0"
- "From\0Joe Perches <joe@perches.com>\0"
- "Subject\0Re: [PATCH 3/3] nvme: fix eui_show() print format\0"
+ "From\0joe@perches.com (Joe Perches)\0"
+ "Subject\0[PATCH 3/3] nvme: fix eui_show() print format\0"
  "Date\0Fri, 03 Nov 2017 08:16:37 -0700\0"
- "To\0Christoph Hellwig <hch@lst.de>"
- " Javier Gonz\303\241lez <jg@lightnvm.io>\0"
- "Cc\0linux-block@vger.kernel.org"
-  sagi@grimberg.me
-  linux-kernel@vger.kernel.org
-  linux-nvme@lists.infradead.org
-  keith.busch@intel.com
- " Javier Gonz\303\241lez <javier@cnexlabs.com>\0"
  "\00:1\0"
  "b\0"
- "On Fri, 2017-11-03 at 13:55 +0100, Christoph Hellwig wrote:\n"
- "> On Fri, Nov 03, 2017 at 11:02:50AM +0100, Javier Gonz=E1lez wrote:\n"
- "> > Signed-off-by: Javier Gonz=E1lez <javier@cnexlabs.com>\n"
+ "On Fri, 2017-11-03@13:55 +0100, Christoph Hellwig wrote:\n"
+ "> On Fri, Nov 03, 2017@11:02:50AM +0100, Javier Gonz?lez wrote:\n"
+ "> > Signed-off-by: Javier Gonz?lez <javier at cnexlabs.com>\n"
  "[]\n"
  "> > diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c\n"
  "[]\n"
- "> > @@ -2108,7 +2108,7 @@ static ssize_t eui_show(struct device *dev, struc=\n"
- "t device_attribute *attr,\n"
+ "> > @@ -2108,7 +2108,7 @@ static ssize_t eui_show(struct device *dev, struct device_attribute *attr,\n"
  "> >  \t\t\t\t\t\t\t\tchar *buf)\n"
  "> >  {\n"
- "> >  \tstruct nvme_ns *ns =3D nvme_get_ns_from_dev(dev);\n"
+ "> >  \tstruct nvme_ns *ns = nvme_get_ns_from_dev(dev);\n"
  "> > -\treturn sprintf(buf, \"%8phd\\n\", ns->eui);\n"
  "> > +\treturn sprintf(buf, \"%8phD\\n\", ns->eui);\n"
  "> >  }\n"
  "> >  static DEVICE_ATTR(eui, S_IRUGO, eui_show, NULL);\n"
- "> =\n"
- "\n"
+ "> \n"
  "> This looks correct.  I wonder what the old code printed - does someone\n"
  "> have a device with an EUI-64 at hand to quickly cross check what we\n"
  "> did before?\n"
@@ -47,13 +37,6 @@
  "\n"
  "\t%8ph\n"
  "\n"
- "without D\n"
- "\n"
- "\n"
- "\n"
- "_______________________________________________\n"
- "Linux-nvme mailing list\n"
- "Linux-nvme@lists.infradead.org\n"
- http://lists.infradead.org/mailman/listinfo/linux-nvme
+ without D
 
-ec8d8f00afd1c18ee73a654c738f493717026a20ac2a58c0019053777f62de73
+94a89ae3666d0a8c67b81261b9b4e886a71fc882bfbc2875eabb5cbf4a0d90bc

diff --git a/a/1.txt b/N2/1.txt
index eda27ee..7f7d067 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -1,20 +1,18 @@
 On Fri, 2017-11-03 at 13:55 +0100, Christoph Hellwig wrote:
-> On Fri, Nov 03, 2017 at 11:02:50AM +0100, Javier Gonz=E1lez wrote:
-> > Signed-off-by: Javier Gonz=E1lez <javier@cnexlabs.com>
+> On Fri, Nov 03, 2017 at 11:02:50AM +0100, Javier González wrote:
+> > Signed-off-by: Javier González <javier@cnexlabs.com>
 []
 > > diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
 []
-> > @@ -2108,7 +2108,7 @@ static ssize_t eui_show(struct device *dev, struc=
-t device_attribute *attr,
+> > @@ -2108,7 +2108,7 @@ static ssize_t eui_show(struct device *dev, struct device_attribute *attr,
 > >  								char *buf)
 > >  {
-> >  	struct nvme_ns *ns =3D nvme_get_ns_from_dev(dev);
+> >  	struct nvme_ns *ns = nvme_get_ns_from_dev(dev);
 > > -	return sprintf(buf, "%8phd\n", ns->eui);
 > > +	return sprintf(buf, "%8phD\n", ns->eui);
 > >  }
 > >  static DEVICE_ATTR(eui, S_IRUGO, eui_show, NULL);
-> =
-
+> 
 > This looks correct.  I wonder what the old code printed - does someone
 > have a device with an EUI-64 at hand to quickly cross check what we
 > did before?
@@ -32,10 +30,3 @@ Perhaps this should just become
 	%8ph
 
 without D
-
-
-
-_______________________________________________
-Linux-nvme mailing list
-Linux-nvme@lists.infradead.org
-http://lists.infradead.org/mailman/listinfo/linux-nvme
diff --git a/a/content_digest b/N2/content_digest
index 2b849d0..5ebd791 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -6,31 +6,29 @@
  "Date\0Fri, 03 Nov 2017 08:16:37 -0700\0"
  "To\0Christoph Hellwig <hch@lst.de>"
  " Javier Gonz\303\241lez <jg@lightnvm.io>\0"
- "Cc\0linux-block@vger.kernel.org"
-  sagi@grimberg.me
-  linux-kernel@vger.kernel.org
-  linux-nvme@lists.infradead.org
+ "Cc\0sagi@grimberg.me"
   keith.busch@intel.com
+  linux-nvme@lists.infradead.org
+  linux-block@vger.kernel.org
+  linux-kernel@vger.kernel.org
  " Javier Gonz\303\241lez <javier@cnexlabs.com>\0"
  "\00:1\0"
  "b\0"
  "On Fri, 2017-11-03 at 13:55 +0100, Christoph Hellwig wrote:\n"
- "> On Fri, Nov 03, 2017 at 11:02:50AM +0100, Javier Gonz=E1lez wrote:\n"
- "> > Signed-off-by: Javier Gonz=E1lez <javier@cnexlabs.com>\n"
+ "> On Fri, Nov 03, 2017 at 11:02:50AM +0100, Javier Gonz\303\241lez wrote:\n"
+ "> > Signed-off-by: Javier Gonz\303\241lez <javier@cnexlabs.com>\n"
  "[]\n"
  "> > diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c\n"
  "[]\n"
- "> > @@ -2108,7 +2108,7 @@ static ssize_t eui_show(struct device *dev, struc=\n"
- "t device_attribute *attr,\n"
+ "> > @@ -2108,7 +2108,7 @@ static ssize_t eui_show(struct device *dev, struct device_attribute *attr,\n"
  "> >  \t\t\t\t\t\t\t\tchar *buf)\n"
  "> >  {\n"
- "> >  \tstruct nvme_ns *ns =3D nvme_get_ns_from_dev(dev);\n"
+ "> >  \tstruct nvme_ns *ns = nvme_get_ns_from_dev(dev);\n"
  "> > -\treturn sprintf(buf, \"%8phd\\n\", ns->eui);\n"
  "> > +\treturn sprintf(buf, \"%8phD\\n\", ns->eui);\n"
  "> >  }\n"
  "> >  static DEVICE_ATTR(eui, S_IRUGO, eui_show, NULL);\n"
- "> =\n"
- "\n"
+ "> \n"
  "> This looks correct.  I wonder what the old code printed - does someone\n"
  "> have a device with an EUI-64 at hand to quickly cross check what we\n"
  "> did before?\n"
@@ -47,13 +45,6 @@
  "\n"
  "\t%8ph\n"
  "\n"
- "without D\n"
- "\n"
- "\n"
- "\n"
- "_______________________________________________\n"
- "Linux-nvme mailing list\n"
- "Linux-nvme@lists.infradead.org\n"
- http://lists.infradead.org/mailman/listinfo/linux-nvme
+ without D
 
-ec8d8f00afd1c18ee73a654c738f493717026a20ac2a58c0019053777f62de73
+137bc2885cdd1723980eb7ab8816b4e122469ac50c63c7ec7f3491b63bd9ca62

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.