All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20160209154215.GF24522@x1>

diff --git a/a/1.txt b/N1/1.txt
index 56877db..86f045b 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -3,44 +3,46 @@ On Sat, 30 Jan 2016, Laxman Dewangan wrote:
 > The MAXIM PMIC MAX77620 and MAX20024 are power management IC
 > which supports RTC, GPIO, DCDC/LDO regulators, interrupt,
 > watchdog etc.
-> 
+>=20
 > Add DT binding document for the different functionality of
 > this device.
-> 
+>=20
 > Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
 > Acked-by: Rob Herring <robh@kernel.org>
 > ---
-> Changes from V1: 
+> Changes from V1:=20
 > - Added units in some of properties.
 > - Change the boolean property to tristate type and detail some of
 >   properties.
-> 
-> Change from V2: 
+>=20
+> Change from V2:=20
 > - added unit in period related dt property.
-> 
+>=20
 > Change from V3: None
 > - Added Rob's ack.
-> 
-> Changes from V4: 
+>=20
+> Changes from V4:=20
 > - A- Provide more details in the dt binding doc.
 > - Take care of fps nodes.
 > - Split the submodule's DT binding doc on respective folder.
 > - Drop the battery charger and low battery binding and related code as
 >   it need to go on power driver.
-> 
+>=20
 > Change from V5:
 > - None
-> 
+>=20
 > Change from V6:
 > -start the patch title with mfd instead of DT: mfd:
-> 
->  Documentation/devicetree/bindings/mfd/max77620.txt | 118 +++++++++++++++++++++
+>=20
+>  Documentation/devicetree/bindings/mfd/max77620.txt | 118 +++++++++++++++=
+++++++
 >  include/dt-bindings/mfd/max77620.h                 |  35 ++++++
 >  2 files changed, 153 insertions(+)
 >  create mode 100644 Documentation/devicetree/bindings/mfd/max77620.txt
 >  create mode 100644 include/dt-bindings/mfd/max77620.h
-> 
-> diff --git a/Documentation/devicetree/bindings/mfd/max77620.txt b/Documentation/devicetree/bindings/mfd/max77620.txt
+>=20
+> diff --git a/Documentation/devicetree/bindings/mfd/max77620.txt b/Documen=
+tation/devicetree/bindings/mfd/max77620.txt
 > new file mode 100644
 > index 0000000..f258ce4
 > --- /dev/null
@@ -62,14 +64,16 @@ On Sat, 30 Jan 2016, Laxman Dewangan wrote:
 
 Nit: Sometimes you use full-stops and sometimes you don't.
 
-> +- interrupt-controller: Marks the device node as an interrupt controller.
+> +- interrupt-controller: Marks the device node as an interrupt controller=
+.
 > +- #interrupt-cells:	is <2> and their usage is compliant to the 2 cells
 > +			variant of <../interrupt-controller/interrupts.txt>
 > +			IRQ numbers for different interrupt source of MAX77620
 > +			are defined at dt-bindings/mfd/max77620.h.
 > +
 > +Optional subnodes and their properties:
-> +=======================================
+> +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
+=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
 > +
 > +Flexible power sequence configurations:
 > +--------------------------------------
@@ -85,7 +89,8 @@ s/mode/modes/
 "can go on OFF state"?
 
 > +		their configurations.
-> +	Global Low power mode (GLPM): In this mode, step-down regulators, linear
+> +	Global Low power mode (GLPM): In this mode, step-down regulators, linea=
+r
 > +		regulators, and the 32kHz oscillator are in low-power modes.
 
 Again, please standardise your formatting.  Sometimes you use
@@ -103,7 +108,8 @@ Global Low Power mode:	In GLPM, step-down regulators, linear
 			regulators, and the 32kHz oscillator are in low-power modes.
 
 > +	Different modes of regulators/clock/GPIOs are controlled by the their
-> +FPS configurations. There is different configuration registers for each of
+> +FPS configurations. There is different configuration registers for each =
+of
 > +these resources. Typical configurations per resource are:
 > +	FPS source: 	Attach the resource to required FPS source. When
 > +			resources are attached to one of FPS source then
@@ -141,7 +147,8 @@ s/on/in/
 > +
 > +The configuration parameters of FPS is provided through subnode "fps"
 > +and their child for FPS specific.
-> +The node name for FPS child are defined as "fps0", "fps1", and "fps2" for
+> +The node name for FPS child are defined as "fps0", "fps1", and "fps2" fo=
+r
 > +the FPS0, FPS1 and FPS2 respectively.
 > +
 > +There is need for different FPS configuration parameters based on system
@@ -168,15 +175,18 @@ s/on/in/
 We already have bindings for sleeping.  Please use a generic one.
 
 > +				    when the FPS control input become active.
-> +-maxim,enable-global-lpm: 	    Boolean, enable Global Low Power Mode (GLPM)
+> +-maxim,enable-global-lpm: 	    Boolean, enable Global Low Power Mode (GL=
+PM)
 > +				    of PMIC when the FPS control input become
 > +				    active.
 > +
 > +Here supported time periods by device in microseconds are as follows:
-> +MAX77620 supports 40, 80, 160, 320, 640, 1280, 2560 and 5120 microseconds.
+> +MAX77620 supports 40, 80, 160, 320, 640, 1280, 2560 and 5120 microsecond=
+s.
 > +MAX20024 supports 20, 40, 80, 160, 320, 640, 1280 and 2540 microseconds.
 > +
-> +For different sub modules like GPIO, pincontrol, regulator, power, please refer
+> +For different sub modules like GPIO, pincontrol, regulator, power, pleas=
+e refer
 > +respected device-tree binding document on respective directories.
 > +
 > +Example:
@@ -184,33 +194,34 @@ We already have bindings for sleeping.  Please use a generic one.
 > +#include <dt-bindings/mfd/max77620.h>
 > +
 > +max77620@3c {
-> +	compatible = "maxim,max77620";
-> +	reg = <0x3c>;
+> +	compatible =3D "maxim,max77620";
+> +	reg =3D <0x3c>;
 > +
-> +	interrupt-parent = <&intc>;
-> +	interrupts = <0 86 IRQ_TYPE_NONE>;
+> +	interrupt-parent =3D <&intc>;
+> +	interrupts =3D <0 86 IRQ_TYPE_NONE>;
 > +
 > +	interrupt-controller;
-> +	#interrupt-cells = <2>;
+> +	#interrupt-cells =3D <2>;
 > +
 > +	fps {
 > +		fps0 {
-> +			maxim,shutdown-fps-time-period-us = <1280>;
-> +			maxim,fps-control = <FPS_CONTROL_SRC_EN1>;
+> +			maxim,shutdown-fps-time-period-us =3D <1280>;
+> +			maxim,fps-control =3D <FPS_CONTROL_SRC_EN1>;
 > +		};
 > +
 > +		fps1 {
-> +			maxim,shutdown-fps-time-period-us = <1280>;
-> +			maxim,fps-control = <FPS_CONTROL_SRC_EN0>;
+> +			maxim,shutdown-fps-time-period-us =3D <1280>;
+> +			maxim,fps-control =3D <FPS_CONTROL_SRC_EN0>;
 > +		};
 > +
 > +		fps2 {
-> +			maxim,shutdown-fps-time-period-us = <1280>;
-> +			maxim,fps-control = <FPS_CONTROL_SRC_SW>;
+> +			maxim,shutdown-fps-time-period-us =3D <1280>;
+> +			maxim,fps-control =3D <FPS_CONTROL_SRC_SW>;
 > +		};
 > +	};
 > +};
-> diff --git a/include/dt-bindings/mfd/max77620.h b/include/dt-bindings/mfd/max77620.h
+> diff --git a/include/dt-bindings/mfd/max77620.h b/include/dt-bindings/mfd=
+/max77620.h
 > new file mode 100644
 > index 0000000..1b571d7
 > --- /dev/null
@@ -252,12 +263,21 @@ We already have bindings for sleeping.  Please use a generic one.
 > +
 > +#endif
 
--- 
+--=20
 Lee Jones
 Linaro STMicroelectronics Landing Team Lead
-Linaro.org │ Open source software for ARM SoCs
+Linaro.org =E2=94=82 Open source software for ARM SoCs
 Follow Linaro: Facebook | Twitter | Blog
---
-To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
-the body of a message to majordomo@vger.kernel.org
-More majordomo info at  http://vger.kernel.org/majordomo-info.html
+
+--=20
+--=20
+You received this message because you are subscribed to "rtc-linux".
+Membership options at http://groups.google.com/group/rtc-linux .
+Please read http://groups.google.com/group/rtc-linux/web/checklist
+before submitting a driver.
+---=20
+You received this message because you are subscribed to the Google Groups "=
+rtc-linux" group.
+To unsubscribe from this group and stop receiving emails from it, send an e=
+mail to rtc-linux+unsubscribe@googlegroups.com.
+For more options, visit https://groups.google.com/d/optout.
diff --git a/a/content_digest b/N1/content_digest
index 6cdd071..f160c6a 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,7 +1,7 @@
  "ref\01454171931-27752-1-git-send-email-ldewangan@nvidia.com\0"
  "ref\01454171931-27752-2-git-send-email-ldewangan@nvidia.com\0"
  "From\0Lee Jones <lee.jones@linaro.org>\0"
- "Subject\0Re: [PATCH V7 1/8] mfd: add device-tree binding doc for PMIC max77620/max20024\0"
+ "Subject\0[rtc-linux] Re: [PATCH V7 1/8] mfd: add device-tree binding doc for PMIC max77620/max20024\0"
  "Date\0Tue, 9 Feb 2016 15:42:15 +0000\0"
  "To\0Laxman Dewangan <ldewangan@nvidia.com>\0"
  "Cc\0robh+dt@kernel.org"
@@ -30,44 +30,46 @@
  "> The MAXIM PMIC MAX77620 and MAX20024 are power management IC\n"
  "> which supports RTC, GPIO, DCDC/LDO regulators, interrupt,\n"
  "> watchdog etc.\n"
- "> \n"
+ ">=20\n"
  "> Add DT binding document for the different functionality of\n"
  "> this device.\n"
- "> \n"
+ ">=20\n"
  "> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>\n"
  "> Acked-by: Rob Herring <robh@kernel.org>\n"
  "> ---\n"
- "> Changes from V1: \n"
+ "> Changes from V1:=20\n"
  "> - Added units in some of properties.\n"
  "> - Change the boolean property to tristate type and detail some of\n"
  ">   properties.\n"
- "> \n"
- "> Change from V2: \n"
+ ">=20\n"
+ "> Change from V2:=20\n"
  "> - added unit in period related dt property.\n"
- "> \n"
+ ">=20\n"
  "> Change from V3: None\n"
  "> - Added Rob's ack.\n"
- "> \n"
- "> Changes from V4: \n"
+ ">=20\n"
+ "> Changes from V4:=20\n"
  "> - A- Provide more details in the dt binding doc.\n"
  "> - Take care of fps nodes.\n"
  "> - Split the submodule's DT binding doc on respective folder.\n"
  "> - Drop the battery charger and low battery binding and related code as\n"
  ">   it need to go on power driver.\n"
- "> \n"
+ ">=20\n"
  "> Change from V5:\n"
  "> - None\n"
- "> \n"
+ ">=20\n"
  "> Change from V6:\n"
  "> -start the patch title with mfd instead of DT: mfd:\n"
- "> \n"
- ">  Documentation/devicetree/bindings/mfd/max77620.txt | 118 +++++++++++++++++++++\n"
+ ">=20\n"
+ ">  Documentation/devicetree/bindings/mfd/max77620.txt | 118 +++++++++++++++=\n"
+ "++++++\n"
  ">  include/dt-bindings/mfd/max77620.h                 |  35 ++++++\n"
  ">  2 files changed, 153 insertions(+)\n"
  ">  create mode 100644 Documentation/devicetree/bindings/mfd/max77620.txt\n"
  ">  create mode 100644 include/dt-bindings/mfd/max77620.h\n"
- "> \n"
- "> diff --git a/Documentation/devicetree/bindings/mfd/max77620.txt b/Documentation/devicetree/bindings/mfd/max77620.txt\n"
+ ">=20\n"
+ "> diff --git a/Documentation/devicetree/bindings/mfd/max77620.txt b/Documen=\n"
+ "tation/devicetree/bindings/mfd/max77620.txt\n"
  "> new file mode 100644\n"
  "> index 0000000..f258ce4\n"
  "> --- /dev/null\n"
@@ -89,14 +91,16 @@
  "\n"
  "Nit: Sometimes you use full-stops and sometimes you don't.\n"
  "\n"
- "> +- interrupt-controller: Marks the device node as an interrupt controller.\n"
+ "> +- interrupt-controller: Marks the device node as an interrupt controller=\n"
+ ".\n"
  "> +- #interrupt-cells:\tis <2> and their usage is compliant to the 2 cells\n"
  "> +\t\t\tvariant of <../interrupt-controller/interrupts.txt>\n"
  "> +\t\t\tIRQ numbers for different interrupt source of MAX77620\n"
  "> +\t\t\tare defined at dt-bindings/mfd/max77620.h.\n"
  "> +\n"
  "> +Optional subnodes and their properties:\n"
- "> +=======================================\n"
+ "> +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=\n"
+ "=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D\n"
  "> +\n"
  "> +Flexible power sequence configurations:\n"
  "> +--------------------------------------\n"
@@ -112,7 +116,8 @@
  "\"can go on OFF state\"?\n"
  "\n"
  "> +\t\ttheir configurations.\n"
- "> +\tGlobal Low power mode (GLPM): In this mode, step-down regulators, linear\n"
+ "> +\tGlobal Low power mode (GLPM): In this mode, step-down regulators, linea=\n"
+ "r\n"
  "> +\t\tregulators, and the 32kHz oscillator are in low-power modes.\n"
  "\n"
  "Again, please standardise your formatting.  Sometimes you use\n"
@@ -130,7 +135,8 @@
  "\t\t\tregulators, and the 32kHz oscillator are in low-power modes.\n"
  "\n"
  "> +\tDifferent modes of regulators/clock/GPIOs are controlled by the their\n"
- "> +FPS configurations. There is different configuration registers for each of\n"
+ "> +FPS configurations. There is different configuration registers for each =\n"
+ "of\n"
  "> +these resources. Typical configurations per resource are:\n"
  "> +\tFPS source: \tAttach the resource to required FPS source. When\n"
  "> +\t\t\tresources are attached to one of FPS source then\n"
@@ -168,7 +174,8 @@
  "> +\n"
  "> +The configuration parameters of FPS is provided through subnode \"fps\"\n"
  "> +and their child for FPS specific.\n"
- "> +The node name for FPS child are defined as \"fps0\", \"fps1\", and \"fps2\" for\n"
+ "> +The node name for FPS child are defined as \"fps0\", \"fps1\", and \"fps2\" fo=\n"
+ "r\n"
  "> +the FPS0, FPS1 and FPS2 respectively.\n"
  "> +\n"
  "> +There is need for different FPS configuration parameters based on system\n"
@@ -195,15 +202,18 @@
  "We already have bindings for sleeping.  Please use a generic one.\n"
  "\n"
  "> +\t\t\t\t    when the FPS control input become active.\n"
- "> +-maxim,enable-global-lpm: \t    Boolean, enable Global Low Power Mode (GLPM)\n"
+ "> +-maxim,enable-global-lpm: \t    Boolean, enable Global Low Power Mode (GL=\n"
+ "PM)\n"
  "> +\t\t\t\t    of PMIC when the FPS control input become\n"
  "> +\t\t\t\t    active.\n"
  "> +\n"
  "> +Here supported time periods by device in microseconds are as follows:\n"
- "> +MAX77620 supports 40, 80, 160, 320, 640, 1280, 2560 and 5120 microseconds.\n"
+ "> +MAX77620 supports 40, 80, 160, 320, 640, 1280, 2560 and 5120 microsecond=\n"
+ "s.\n"
  "> +MAX20024 supports 20, 40, 80, 160, 320, 640, 1280 and 2540 microseconds.\n"
  "> +\n"
- "> +For different sub modules like GPIO, pincontrol, regulator, power, please refer\n"
+ "> +For different sub modules like GPIO, pincontrol, regulator, power, pleas=\n"
+ "e refer\n"
  "> +respected device-tree binding document on respective directories.\n"
  "> +\n"
  "> +Example:\n"
@@ -211,33 +221,34 @@
  "> +#include <dt-bindings/mfd/max77620.h>\n"
  "> +\n"
  "> +max77620@3c {\n"
- "> +\tcompatible = \"maxim,max77620\";\n"
- "> +\treg = <0x3c>;\n"
+ "> +\tcompatible =3D \"maxim,max77620\";\n"
+ "> +\treg =3D <0x3c>;\n"
  "> +\n"
- "> +\tinterrupt-parent = <&intc>;\n"
- "> +\tinterrupts = <0 86 IRQ_TYPE_NONE>;\n"
+ "> +\tinterrupt-parent =3D <&intc>;\n"
+ "> +\tinterrupts =3D <0 86 IRQ_TYPE_NONE>;\n"
  "> +\n"
  "> +\tinterrupt-controller;\n"
- "> +\t#interrupt-cells = <2>;\n"
+ "> +\t#interrupt-cells =3D <2>;\n"
  "> +\n"
  "> +\tfps {\n"
  "> +\t\tfps0 {\n"
- "> +\t\t\tmaxim,shutdown-fps-time-period-us = <1280>;\n"
- "> +\t\t\tmaxim,fps-control = <FPS_CONTROL_SRC_EN1>;\n"
+ "> +\t\t\tmaxim,shutdown-fps-time-period-us =3D <1280>;\n"
+ "> +\t\t\tmaxim,fps-control =3D <FPS_CONTROL_SRC_EN1>;\n"
  "> +\t\t};\n"
  "> +\n"
  "> +\t\tfps1 {\n"
- "> +\t\t\tmaxim,shutdown-fps-time-period-us = <1280>;\n"
- "> +\t\t\tmaxim,fps-control = <FPS_CONTROL_SRC_EN0>;\n"
+ "> +\t\t\tmaxim,shutdown-fps-time-period-us =3D <1280>;\n"
+ "> +\t\t\tmaxim,fps-control =3D <FPS_CONTROL_SRC_EN0>;\n"
  "> +\t\t};\n"
  "> +\n"
  "> +\t\tfps2 {\n"
- "> +\t\t\tmaxim,shutdown-fps-time-period-us = <1280>;\n"
- "> +\t\t\tmaxim,fps-control = <FPS_CONTROL_SRC_SW>;\n"
+ "> +\t\t\tmaxim,shutdown-fps-time-period-us =3D <1280>;\n"
+ "> +\t\t\tmaxim,fps-control =3D <FPS_CONTROL_SRC_SW>;\n"
  "> +\t\t};\n"
  "> +\t};\n"
  "> +};\n"
- "> diff --git a/include/dt-bindings/mfd/max77620.h b/include/dt-bindings/mfd/max77620.h\n"
+ "> diff --git a/include/dt-bindings/mfd/max77620.h b/include/dt-bindings/mfd=\n"
+ "/max77620.h\n"
  "> new file mode 100644\n"
  "> index 0000000..1b571d7\n"
  "> --- /dev/null\n"
@@ -279,14 +290,23 @@
  "> +\n"
  "> +#endif\n"
  "\n"
- "-- \n"
+ "--=20\n"
  "Lee Jones\n"
  "Linaro STMicroelectronics Landing Team Lead\n"
- "Linaro.org \342\224\202 Open source software for ARM SoCs\n"
+ "Linaro.org =E2=94=82 Open source software for ARM SoCs\n"
  "Follow Linaro: Facebook | Twitter | Blog\n"
- "--\n"
- "To unsubscribe from this list: send the line \"unsubscribe linux-gpio\" in\n"
- "the body of a message to majordomo@vger.kernel.org\n"
- More majordomo info at  http://vger.kernel.org/majordomo-info.html
+ "\n"
+ "--=20\n"
+ "--=20\n"
+ "You received this message because you are subscribed to \"rtc-linux\".\n"
+ "Membership options at http://groups.google.com/group/rtc-linux .\n"
+ "Please read http://groups.google.com/group/rtc-linux/web/checklist\n"
+ "before submitting a driver.\n"
+ "---=20\n"
+ "You received this message because you are subscribed to the Google Groups \"=\n"
+ "rtc-linux\" group.\n"
+ "To unsubscribe from this group and stop receiving emails from it, send an e=\n"
+ "mail to rtc-linux+unsubscribe@googlegroups.com.\n"
+ For more options, visit https://groups.google.com/d/optout.
 
-ca2467a716a6adfb6ebda3367c8d163b1121befe68962fb5743689912a3e6ffe
+8d8339fa2449a47c1334ac54026275e5e63bf67a7e52022e5c5f42d443b2b194

diff --git a/a/1.txt b/N2/1.txt
index 56877db..06e4ce4 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -257,7 +257,3 @@ Lee Jones
 Linaro STMicroelectronics Landing Team Lead
 Linaro.org │ Open source software for ARM SoCs
 Follow Linaro: Facebook | Twitter | Blog
---
-To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
-the body of a message to majordomo@vger.kernel.org
-More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff --git a/a/content_digest b/N2/content_digest
index 6cdd071..a5e4d0f 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -283,10 +283,6 @@
  "Lee Jones\n"
  "Linaro STMicroelectronics Landing Team Lead\n"
  "Linaro.org \342\224\202 Open source software for ARM SoCs\n"
- "Follow Linaro: Facebook | Twitter | Blog\n"
- "--\n"
- "To unsubscribe from this list: send the line \"unsubscribe linux-gpio\" in\n"
- "the body of a message to majordomo@vger.kernel.org\n"
- More majordomo info at  http://vger.kernel.org/majordomo-info.html
+ Follow Linaro: Facebook | Twitter | Blog
 
-ca2467a716a6adfb6ebda3367c8d163b1121befe68962fb5743689912a3e6ffe
+d6227e00cdb7fa534fcf53304b026d9de8e165eaad46fe04b49c9a423a7333cb

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.