All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <5720C750.3050104@phytec.de>

diff --git a/a/1.txt b/N1/1.txt
index 822f7b5..c4bc8bd 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -2,12 +2,11 @@
 
 On 27.04.2016 15:50, Mark Brown wrote:
 > On Wed, Apr 27, 2016 at 08:35:46AM +0200, Wadim Egorov wrote:
->> On 26.04.2016 21:33, Heiko St=FCbner wrote:
->>> with this patch applied, 4.6.0-rc5-next-20160426 fails to boot on=20
+>> On 26.04.2016 21:33, Heiko Stübner wrote:
+>>> with this patch applied, 4.6.0-rc5-next-20160426 fails to boot on 
 >>> rk3288-veyron devices with the bug below. Reverting this one patch
 >>> results in the system booting again:
->> This is because I missed to add the correct ops for LDO=5FREG3 in this p=
-atch.
+>> This is because I missed to add the correct ops for LDO_REG3 in this patch.
 > Any ETA on a fix or should I revert?
 this patch
 
@@ -16,5 +15,4 @@ http://lists.infradead.org/pipermail/linux-rockchip/2016-April/008674.html
 will fix the issue.
 
 The regulator patches from v4 are based on top of
-commit 4a5ed8c1adc3 ("regulator: rk808: remove unused rk808=5Freg=5Fops=5Fr=
-anges")
+commit 4a5ed8c1adc3 ("regulator: rk808: remove unused rk808_reg_ops_ranges")
diff --git a/a/content_digest b/N1/content_digest
index 2905f49..11a25cc 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -31,12 +31,11 @@
  "\n"
  "On 27.04.2016 15:50, Mark Brown wrote:\n"
  "> On Wed, Apr 27, 2016 at 08:35:46AM +0200, Wadim Egorov wrote:\n"
- ">> On 26.04.2016 21:33, Heiko St=FCbner wrote:\n"
- ">>> with this patch applied, 4.6.0-rc5-next-20160426 fails to boot on=20\n"
+ ">> On 26.04.2016 21:33, Heiko St\303\274bner wrote:\n"
+ ">>> with this patch applied, 4.6.0-rc5-next-20160426 fails to boot on \n"
  ">>> rk3288-veyron devices with the bug below. Reverting this one patch\n"
  ">>> results in the system booting again:\n"
- ">> This is because I missed to add the correct ops for LDO=5FREG3 in this p=\n"
- "atch.\n"
+ ">> This is because I missed to add the correct ops for LDO_REG3 in this patch.\n"
  "> Any ETA on a fix or should I revert?\n"
  "this patch\n"
  "\n"
@@ -45,7 +44,6 @@
  "will fix the issue.\n"
  "\n"
  "The regulator patches from v4 are based on top of\n"
- "commit 4a5ed8c1adc3 (\"regulator: rk808: remove unused rk808=5Freg=5Fops=5Fr=\n"
- "anges\")"
+ "commit 4a5ed8c1adc3 (\"regulator: rk808: remove unused rk808_reg_ops_ranges\")"
 
-62e9807464986652eba799eab63d7763ae8e7f4197173f9e9399ddab720f57d0
+b241c7773984c9f8f6feec2d0cc19bfffe936be23fea1b219a6262176278e744

diff --git a/a/1.txt b/N2/1.txt
index 822f7b5..997cfea 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -2,12 +2,12 @@
 
 On 27.04.2016 15:50, Mark Brown wrote:
 > On Wed, Apr 27, 2016 at 08:35:46AM +0200, Wadim Egorov wrote:
->> On 26.04.2016 21:33, Heiko St=FCbner wrote:
+>> On 26.04.2016 21:33, Heiko St=C3=BCbner wrote:
 >>> with this patch applied, 4.6.0-rc5-next-20160426 fails to boot on=20
 >>> rk3288-veyron devices with the bug below. Reverting this one patch
 >>> results in the system booting again:
->> This is because I missed to add the correct ops for LDO=5FREG3 in this p=
-atch.
+>> This is because I missed to add the correct ops for LDO_REG3 in this pat=
+ch.
 > Any ETA on a fix or should I revert?
 this patch
 
@@ -16,5 +16,18 @@ http://lists.infradead.org/pipermail/linux-rockchip/2016-April/008674.html
 will fix the issue.
 
 The regulator patches from v4 are based on top of
-commit 4a5ed8c1adc3 ("regulator: rk808: remove unused rk808=5Freg=5Fops=5Fr=
-anges")
+commit 4a5ed8c1adc3 ("regulator: rk808: remove unused rk808_reg_ops_ranges"=
+)
+
+--=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/N2/content_digest
index 2905f49..3488bbb 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -3,7 +3,7 @@
  "ref\057205DC2.7070506@phytec.de\0"
  "ref\020160427135048.GQ3217@sirena.org.uk\0"
  "From\0Wadim Egorov <w.egorov@phytec.de>\0"
- "Subject\0Re: Applied \"regulator: rk808: remove linear range definitions with a single range\" to the regulator tree\0"
+ "Subject\0[rtc-linux] Re: Applied \"regulator: rk808: remove linear range definitions with a single range\" to the regulator tree\0"
  "Date\0Wed, 27 Apr 2016 16:06:08 +0200\0"
  "To\0Mark Brown <broonie@kernel.org>\0"
  "Cc\0Heiko St\303\274bner <heiko@sntech.de>"
@@ -31,12 +31,12 @@
  "\n"
  "On 27.04.2016 15:50, Mark Brown wrote:\n"
  "> On Wed, Apr 27, 2016 at 08:35:46AM +0200, Wadim Egorov wrote:\n"
- ">> On 26.04.2016 21:33, Heiko St=FCbner wrote:\n"
+ ">> On 26.04.2016 21:33, Heiko St=C3=BCbner wrote:\n"
  ">>> with this patch applied, 4.6.0-rc5-next-20160426 fails to boot on=20\n"
  ">>> rk3288-veyron devices with the bug below. Reverting this one patch\n"
  ">>> results in the system booting again:\n"
- ">> This is because I missed to add the correct ops for LDO=5FREG3 in this p=\n"
- "atch.\n"
+ ">> This is because I missed to add the correct ops for LDO_REG3 in this pat=\n"
+ "ch.\n"
  "> Any ETA on a fix or should I revert?\n"
  "this patch\n"
  "\n"
@@ -45,7 +45,20 @@
  "will fix the issue.\n"
  "\n"
  "The regulator patches from v4 are based on top of\n"
- "commit 4a5ed8c1adc3 (\"regulator: rk808: remove unused rk808=5Freg=5Fops=5Fr=\n"
- "anges\")"
+ "commit 4a5ed8c1adc3 (\"regulator: rk808: remove unused rk808_reg_ops_ranges\"=\n"
+ ")\n"
+ "\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.
 
-62e9807464986652eba799eab63d7763ae8e7f4197173f9e9399ddab720f57d0
+f45ed108f5c77f70ec831e18624db562faab56557d3d7cdabca1931145dbbdab

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.