All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <555FCD54.3080306@boundarydevices.com>

diff --git a/a/1.txt b/N1/1.txt
index baa0a72..c7edcab 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -4,13 +4,13 @@ On 05/22/2015 12:30 PM, Peter Seiderer wrote:
 > Hello Philipp,
 > 
 >> Gesendet: Freitag, 22. Mai 2015 um 13:05 Uhr
->> Von: "Philipp Zabel" <p.zabel@pengutronix.de>
+>> Von: "Philipp Zabel" <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
 >> Am Donnerstag, den 21.05.2015, 19:45 +0200 schrieb Peter Seiderer:
 >>>
 >>> <snip>
 >>>
 >>> +
->>> +		reg_can_xcvr: regulator at 3 {
+>>> +		reg_can_xcvr: regulator@3 {
 >>> +			compatible = "regulator-fixed";
 >>> +			reg = <3>;
 >>> +			regulator-name = "CAN XCVR";
@@ -33,7 +33,7 @@ On 05/22/2015 12:30 PM, Peter Seiderer wrote:
 > 
 > I was a bit confused from the original:
 > 
-> imx6qdl-tx6.dtsi:103:           reg_can_xcvr: regulator at 3 {
+> imx6qdl-tx6.dtsi:103:           reg_can_xcvr: regulator@3 {
 > imx6qdl-tx6.dtsi-104-                   compatible = "regulator-fixed";
 > imx6qdl-tx6.dtsi-105-                   reg = <3>;
 > imx6qdl-tx6.dtsi-106-                   regulator-name = "CAN XCVR";
@@ -60,7 +60,7 @@ is the default.
 So if this board really wants an "active high" enable pin, it's likely
 not operating properly:
 
-> imx28-tx28.dts:90:              reg_can_xcvr: regulator at 4 {
+> imx28-tx28.dts:90:              reg_can_xcvr: regulator@4 {
 > imx28-tx28.dts-91-                      compatible = "regulator-fixed";
 > imx28-tx28.dts-92-                      reg = <4>;
 > imx28-tx28.dts-93-                      regulator-name = "CAN XCVR";
@@ -85,7 +85,7 @@ GPIO_ACTIVE_LOW in the gpio reference, but it won't be parsed or
 acted upon.
 
 i.e.
-	reg_can_xcvr: regulator at 3 {
+	reg_can_xcvr: regulator@3 {
 		compatible = "regulator-fixed";
 		reg = <3>;
 		regulator-name = "CAN XCVR";
@@ -100,3 +100,7 @@ Regards,
 
 
 Eric
+--
+To unsubscribe from this list: send the line "unsubscribe devicetree" in
+the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
+More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff --git a/a/content_digest b/N1/content_digest
index ee4223d..9246e41 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,10 +1,22 @@
  "ref\01432230303-3414-1-git-send-email-ps.report@gmx.net\0"
  "ref\01432292734.3929.64.camel@pengutronix.de\0"
  "ref\0trinity-1dc833e7-79e4-4fe4-9e8b-cff88a35a0d9-1432323019162@3capp-gmx-bs48\0"
- "From\0eric.nelson@boundarydevices.com (Eric Nelson)\0"
+ "From\0Eric Nelson <eric.nelson-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>\0"
  "Subject\0Aw: [PATCH v2] ARM: dts: nitrogen6x: add CAN support\0"
  "Date\0Fri, 22 May 2015 17:44:04 -0700\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Peter Seiderer <ps.report-hi6Y0CQ0nG0@public.gmane.org>"
+ " Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>\0"
+ "Cc\0Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>"
+  devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
+  Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
+  Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>
+  Ian Campbell <ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>
+  linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
+  Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
+  Sascha Hauer <kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
+  Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
+  Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
+ " linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org\0"
  "\00:1\0"
  "b\0"
  "Hello Peter,\n"
@@ -13,13 +25,13 @@
  "> Hello Philipp,\n"
  "> \n"
  ">> Gesendet: Freitag, 22. Mai 2015 um 13:05 Uhr\n"
- ">> Von: \"Philipp Zabel\" <p.zabel@pengutronix.de>\n"
+ ">> Von: \"Philipp Zabel\" <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>\n"
  ">> Am Donnerstag, den 21.05.2015, 19:45 +0200 schrieb Peter Seiderer:\n"
  ">>>\n"
  ">>> <snip>\n"
  ">>>\n"
  ">>> +\n"
- ">>> +\t\treg_can_xcvr: regulator at 3 {\n"
+ ">>> +\t\treg_can_xcvr: regulator@3 {\n"
  ">>> +\t\t\tcompatible = \"regulator-fixed\";\n"
  ">>> +\t\t\treg = <3>;\n"
  ">>> +\t\t\tregulator-name = \"CAN XCVR\";\n"
@@ -42,7 +54,7 @@
  "> \n"
  "> I was a bit confused from the original:\n"
  "> \n"
- "> imx6qdl-tx6.dtsi:103:           reg_can_xcvr: regulator at 3 {\n"
+ "> imx6qdl-tx6.dtsi:103:           reg_can_xcvr: regulator@3 {\n"
  "> imx6qdl-tx6.dtsi-104-                   compatible = \"regulator-fixed\";\n"
  "> imx6qdl-tx6.dtsi-105-                   reg = <3>;\n"
  "> imx6qdl-tx6.dtsi-106-                   regulator-name = \"CAN XCVR\";\n"
@@ -69,7 +81,7 @@
  "So if this board really wants an \"active high\" enable pin, it's likely\n"
  "not operating properly:\n"
  "\n"
- "> imx28-tx28.dts:90:              reg_can_xcvr: regulator at 4 {\n"
+ "> imx28-tx28.dts:90:              reg_can_xcvr: regulator@4 {\n"
  "> imx28-tx28.dts-91-                      compatible = \"regulator-fixed\";\n"
  "> imx28-tx28.dts-92-                      reg = <4>;\n"
  "> imx28-tx28.dts-93-                      regulator-name = \"CAN XCVR\";\n"
@@ -94,7 +106,7 @@
  "acted upon.\n"
  "\n"
  "i.e.\n"
- "\treg_can_xcvr: regulator at 3 {\n"
+ "\treg_can_xcvr: regulator@3 {\n"
  "\t\tcompatible = \"regulator-fixed\";\n"
  "\t\treg = <3>;\n"
  "\t\tregulator-name = \"CAN XCVR\";\n"
@@ -108,6 +120,10 @@
  "Regards,\n"
  "\n"
  "\n"
- Eric
+ "Eric\n"
+ "--\n"
+ "To unsubscribe from this list: send the line \"unsubscribe devicetree\" in\n"
+ "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n"
+ More majordomo info at  http://vger.kernel.org/majordomo-info.html
 
-1a0f40d4919d3ca8d7373a94ab87fa1e820a2cdf44573e9cdfbea7f99ed32fe7
+af27a5dc07c2f0eb35b34eb551bd18fc336f7b13697a345bb3b8c51b8055f57e

diff --git a/a/1.txt b/N2/1.txt
index baa0a72..a94e049 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -10,7 +10,7 @@ On 05/22/2015 12:30 PM, Peter Seiderer wrote:
 >>> <snip>
 >>>
 >>> +
->>> +		reg_can_xcvr: regulator at 3 {
+>>> +		reg_can_xcvr: regulator@3 {
 >>> +			compatible = "regulator-fixed";
 >>> +			reg = <3>;
 >>> +			regulator-name = "CAN XCVR";
@@ -33,7 +33,7 @@ On 05/22/2015 12:30 PM, Peter Seiderer wrote:
 > 
 > I was a bit confused from the original:
 > 
-> imx6qdl-tx6.dtsi:103:           reg_can_xcvr: regulator at 3 {
+> imx6qdl-tx6.dtsi:103:           reg_can_xcvr: regulator@3 {
 > imx6qdl-tx6.dtsi-104-                   compatible = "regulator-fixed";
 > imx6qdl-tx6.dtsi-105-                   reg = <3>;
 > imx6qdl-tx6.dtsi-106-                   regulator-name = "CAN XCVR";
@@ -60,7 +60,7 @@ is the default.
 So if this board really wants an "active high" enable pin, it's likely
 not operating properly:
 
-> imx28-tx28.dts:90:              reg_can_xcvr: regulator at 4 {
+> imx28-tx28.dts:90:              reg_can_xcvr: regulator@4 {
 > imx28-tx28.dts-91-                      compatible = "regulator-fixed";
 > imx28-tx28.dts-92-                      reg = <4>;
 > imx28-tx28.dts-93-                      regulator-name = "CAN XCVR";
@@ -85,7 +85,7 @@ GPIO_ACTIVE_LOW in the gpio reference, but it won't be parsed or
 acted upon.
 
 i.e.
-	reg_can_xcvr: regulator at 3 {
+	reg_can_xcvr: regulator@3 {
 		compatible = "regulator-fixed";
 		reg = <3>;
 		regulator-name = "CAN XCVR";
diff --git a/a/content_digest b/N2/content_digest
index ee4223d..4442f99 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -1,10 +1,22 @@
  "ref\01432230303-3414-1-git-send-email-ps.report@gmx.net\0"
  "ref\01432292734.3929.64.camel@pengutronix.de\0"
  "ref\0trinity-1dc833e7-79e4-4fe4-9e8b-cff88a35a0d9-1432323019162@3capp-gmx-bs48\0"
- "From\0eric.nelson@boundarydevices.com (Eric Nelson)\0"
+ "From\0Eric Nelson <eric.nelson@boundarydevices.com>\0"
  "Subject\0Aw: [PATCH v2] ARM: dts: nitrogen6x: add CAN support\0"
  "Date\0Fri, 22 May 2015 17:44:04 -0700\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Peter Seiderer <ps.report@gmx.net>"
+ " Philipp Zabel <p.zabel@pengutronix.de>\0"
+ "Cc\0Mark Rutland <mark.rutland@arm.com>"
+  devicetree@vger.kernel.org
+  Russell King <linux@arm.linux.org.uk>
+  Pawel Moll <pawel.moll@arm.com>
+  Ian Campbell <ijc+devicetree@hellion.org.uk>
+  linux-kernel@vger.kernel.org
+  Rob Herring <robh+dt@kernel.org>
+  Sascha Hauer <kernel@pengutronix.de>
+  Kumar Gala <galak@codeaurora.org>
+  Shawn Guo <shawn.guo@linaro.org>
+ " linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "Hello Peter,\n"
@@ -19,7 +31,7 @@
  ">>> <snip>\n"
  ">>>\n"
  ">>> +\n"
- ">>> +\t\treg_can_xcvr: regulator at 3 {\n"
+ ">>> +\t\treg_can_xcvr: regulator@3 {\n"
  ">>> +\t\t\tcompatible = \"regulator-fixed\";\n"
  ">>> +\t\t\treg = <3>;\n"
  ">>> +\t\t\tregulator-name = \"CAN XCVR\";\n"
@@ -42,7 +54,7 @@
  "> \n"
  "> I was a bit confused from the original:\n"
  "> \n"
- "> imx6qdl-tx6.dtsi:103:           reg_can_xcvr: regulator at 3 {\n"
+ "> imx6qdl-tx6.dtsi:103:           reg_can_xcvr: regulator@3 {\n"
  "> imx6qdl-tx6.dtsi-104-                   compatible = \"regulator-fixed\";\n"
  "> imx6qdl-tx6.dtsi-105-                   reg = <3>;\n"
  "> imx6qdl-tx6.dtsi-106-                   regulator-name = \"CAN XCVR\";\n"
@@ -69,7 +81,7 @@
  "So if this board really wants an \"active high\" enable pin, it's likely\n"
  "not operating properly:\n"
  "\n"
- "> imx28-tx28.dts:90:              reg_can_xcvr: regulator at 4 {\n"
+ "> imx28-tx28.dts:90:              reg_can_xcvr: regulator@4 {\n"
  "> imx28-tx28.dts-91-                      compatible = \"regulator-fixed\";\n"
  "> imx28-tx28.dts-92-                      reg = <4>;\n"
  "> imx28-tx28.dts-93-                      regulator-name = \"CAN XCVR\";\n"
@@ -94,7 +106,7 @@
  "acted upon.\n"
  "\n"
  "i.e.\n"
- "\treg_can_xcvr: regulator at 3 {\n"
+ "\treg_can_xcvr: regulator@3 {\n"
  "\t\tcompatible = \"regulator-fixed\";\n"
  "\t\treg = <3>;\n"
  "\t\tregulator-name = \"CAN XCVR\";\n"
@@ -110,4 +122,4 @@
  "\n"
  Eric
 
-1a0f40d4919d3ca8d7373a94ab87fa1e820a2cdf44573e9cdfbea7f99ed32fe7
+c6ab8dedc933e23b4bb0d23e36f557c119be01676c49f394701796744c851b04

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.