diff for duplicates of <1490701966.3546.24.camel@nxp.com>

diff --git a/a/1.txt b/N1/1.txt
index 90229a2..7771f1d 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -6,7 +6,7 @@ On Fri, 2017-03-24 at 12:54 +0000, Mark Brown wrote:
 > > +		anatop_reg->rdesc.min_dropout_uV = LDO_MIN_DROPOUT_UV;
 > No, this is completely broken - you can't expect to randomly change hthe
 > regulator description at runtime behind the back of the framework and
-> expect things to work.  If there is a need to do this we need an
+> expect things to work.??If there is a need to do this we need an
 > interface for getting the current value and a way to notify of changes.
 > 
 > That said I would not expect the dropout voltage to be considered at
@@ -19,9 +19,3 @@ currently in bypass mode.
 
 In theory a function could be added in regulator_ops to ask a regulator driver
 what requirements it has for its supply but this does not seem necessary.
-
-
-_______________________________________________
-linux-arm-kernel mailing list
-linux-arm-kernel@lists.infradead.org
-http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
diff --git a/a/content_digest b/N1/content_digest
index a98ede2..a245a01 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,26 +1,10 @@
  "ref\0cover.1490199005.git.leonard.crestez@nxp.com\0"
  "ref\0cd944a7223cfe68788c299082a5f262e8bea2136.1490199005.git.leonard.crestez@nxp.com\0"
  "ref\020170324125438.5wy3r2mr3g5eaxvy@sirena.org.uk\0"
- "From\0Leonard Crestez <leonard.crestez@nxp.com>\0"
- "Subject\0Re: [RFC 5/8] regulator: anatop: fix min dropout for bypass mode\0"
+ "From\0leonard.crestez@nxp.com (Leonard Crestez)\0"
+ "Subject\0[RFC 5/8] regulator: anatop: fix min dropout for bypass mode\0"
  "Date\0Tue, 28 Mar 2017 14:52:46 +0300\0"
- "To\0Mark Brown <broonie@kernel.org>\0"
- "Cc\0Mark Rutland <mark.rutland@arm.com>"
-  devicetree@vger.kernel.org
-  Anson Huang <Anson.Huang@nxp.com>
-  Irina Tirdea <irina.tirdea@nxp.com>
-  Viresh Kumar <viresh.kumar@linaro.org>
-  linux-pm@vger.kernel.org
-  Rafael J. Wysocki <rjw@rjwysocki.net>
-  Liam Girdwood <lgirdwood@gmail.com>
-  linux-kernel@vger.kernel.org
-  Rob Herring <robh+dt@kernel.org>
-  Octavian Purdila <octavian.purdila@nxp.com>
-  Sascha Hauer <kernel@pengutronix.de>
-  Fabio Estevam <fabio.estevam@nxp.com>
-  Robin Gong <yibin.gong@nxp.com>
-  Shawn Guo <shawnguo@kernel.org>
- " linux-arm-kernel@lists.infradead.org\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On Fri, 2017-03-24 at 12:54 +0000, Mark Brown wrote:\n"
@@ -31,7 +15,7 @@
  "> > +\t\tanatop_reg->rdesc.min_dropout_uV = LDO_MIN_DROPOUT_UV;\n"
  "> No, this is completely broken - you can't expect to randomly change hthe\n"
  "> regulator description at runtime behind the back of the framework and\n"
- "> expect things to work.\302\240\302\240If there is a need to do this we need an\n"
+ "> expect things to work.??If there is a need to do this we need an\n"
  "> interface for getting the current value and a way to notify of changes.\n"
  "> \n"
  "> That said I would not expect the dropout voltage to be considered at\n"
@@ -43,12 +27,6 @@
  "currently in bypass mode.\n"
  "\n"
  "In theory a function could be added in regulator_ops to ask a regulator driver\n"
- "what requirements it has for its supply but this does not seem necessary.\n"
- "\n"
- "\n"
- "_______________________________________________\n"
- "linux-arm-kernel mailing list\n"
- "linux-arm-kernel@lists.infradead.org\n"
- http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
+ what requirements it has for its supply but this does not seem necessary.
 
-5617f610e40e94b181284bf160e5a7f872440be6438c6f5269f50bcb63a545ce
+9cddc118a6d025bba1edba55d07abbfc0c370c7e2826cd2401752e427701a1c9
