All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <56D6D6AD.7080207@cogentembedded.com>

diff --git a/a/1.txt b/N1/1.txt
index 8ebe126..70dd760 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -22,7 +22,7 @@ On 3/2/2016 10:29 AM, Ramesh Shanmugasundaram wrote:
 >>>      [PATCH] arm64: dts: r8a7795: Add CAN support
 >>>
 >>>      The respective CAN subsystem changes are submitted separately here
->>> (https://www.mail-archive.com/linux-renesas-soc@vger.kernel.org/msg013
+>>> (https://www.mail-archive.com/linux-renesas-soc at vger.kernel.org/msg013
 >>> 88.html)
 >>>
 >>> Thanks,
@@ -40,9 +40,9 @@ On 3/2/2016 10:29 AM, Ramesh Shanmugasundaram wrote:
 >>>    			status = "disabled";
 >>>    		};
 >>>
->>> +		canfd: canfd@e66c0000 {
+>>> +		canfd: canfd at e66c0000 {
 >>
->>      The node name should still be "can@e66c0000", I think.
+>>      The node name should still be "can at e66c0000", I think.
 >
 > Thanks for the review.
 >
@@ -53,7 +53,7 @@ hardware level? I haven't see you posting the CAN-FD driver yet...
 
 > and hence I chose this node name to differentiate. A grep of canfd on sysfs would tell if the controller is enabled. The channels on "net" would still be named "canx".
 >
-> I'll change it if you still feel "can@e66c0000" is more appropriate.
+> I'll change it if you still feel "can at e66c0000" is more appropriate.
 
     It is -- the node names should be generic and ePAPR even has the "can" 
 name listed explicitly in the section 2.2.2.
diff --git a/a/content_digest b/N1/content_digest
index 685810b..421cc0d 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,24 +1,10 @@
  "ref\01456826640-23237-1-git-send-email-ramesh.shanmugasundaram@bp.renesas.com\0"
  "ref\056D59538.2060100@cogentembedded.com\0"
  "ref\0SG2PR06MB1038FBA247777C89F70E2633C3BC0@SG2PR06MB1038.apcprd06.prod.outlook.com\0"
- "From\0Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>\0"
- "Subject\0Re: [PATCH] arm64: dts: r8a7795: Add CAN FD support\0"
+ "From\0sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)\0"
+ "Subject\0[PATCH] arm64: dts: r8a7795: Add CAN FD support\0"
  "Date\0Wed, 2 Mar 2016 15:03:57 +0300\0"
- "To\0Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>"
-  mkl@pengutronix.de <mkl@pengutronix.de>
-  wg@grandegger.com <wg@grandegger.com>
-  horms@verge.net.au <horms@verge.net.au>
-  magnus.damm@gmail.com <magnus.damm@gmail.com>
-  robh+dt@kernel.org <robh+dt@kernel.org>
-  pawel.moll@arm.com <pawel.moll@arm.com>
-  mark.rutland@arm.com <mark.rutland@arm.com>
-  ijc+devicetree@hellion.org.uk <ijc+devicetree@hellion.org.uk>
- " galak@codeaurora.org <galak@codeaurora.org>\0"
- "Cc\0linux-renesas-soc@vger.kernel.org <linux-renesas-soc@vger.kernel.org>"
-  devicetree@vger.kernel.org <devicetree@vger.kernel.org>
-  linux-can@vger.kernel.org <linux-can@vger.kernel.org>
-  linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>
- " Chris Paterson <Chris.Paterson2@renesas.com>\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "Hello.\n"
@@ -45,7 +31,7 @@
  ">>>      [PATCH] arm64: dts: r8a7795: Add CAN support\n"
  ">>>\n"
  ">>>      The respective CAN subsystem changes are submitted separately here\n"
- ">>> (https://www.mail-archive.com/linux-renesas-soc@vger.kernel.org/msg013\n"
+ ">>> (https://www.mail-archive.com/linux-renesas-soc at vger.kernel.org/msg013\n"
  ">>> 88.html)\n"
  ">>>\n"
  ">>> Thanks,\n"
@@ -63,9 +49,9 @@
  ">>>    \t\t\tstatus = \"disabled\";\n"
  ">>>    \t\t};\n"
  ">>>\n"
- ">>> +\t\tcanfd: canfd@e66c0000 {\n"
+ ">>> +\t\tcanfd: canfd at e66c0000 {\n"
  ">>\n"
- ">>      The node name should still be \"can@e66c0000\", I think.\n"
+ ">>      The node name should still be \"can at e66c0000\", I think.\n"
  ">\n"
  "> Thanks for the review.\n"
  ">\n"
@@ -76,7 +62,7 @@
  "\n"
  "> and hence I chose this node name to differentiate. A grep of canfd on sysfs would tell if the controller is enabled. The channels on \"net\" would still be named \"canx\".\n"
  ">\n"
- "> I'll change it if you still feel \"can@e66c0000\" is more appropriate.\n"
+ "> I'll change it if you still feel \"can at e66c0000\" is more appropriate.\n"
  "\n"
  "    It is -- the node names should be generic and ePAPR even has the \"can\" \n"
  "name listed explicitly in the section 2.2.2.\n"
@@ -86,4 +72,4 @@
  "\n"
  MBR, Sergei
 
-e986847ec8f90814665e0a25022aa11b2ea43f26aef633d19ce7a785805e573d
+1cefee770ea0c18a50cef8235fad3a044cae8aa708c7f4549a67bce25f2a27fd

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.