diff for duplicates of <13413437.Ipf2eOczfj@diego> diff --git a/a/1.txt b/N1/1.txt index 0d88e8e..28bfe36 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,22 +1,18 @@ Am Mittwoch, 27. April 2016, 14:50:48 schrieb Mark Brown: > 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= - -> > > rk3288-veyron devices with the bug below. Reverting this one patc= -h -> >=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_REG3 in thi= -s +> > This is because I missed to add the correct ops for LDO_REG3 in this > > patch. ->=20 +> > Any ETA on a fix or should I revert? I guess -=09[PATCH v4 1/7] regulator: rk808: Add rk808_reg_ops_ranges for LDO3 -from yesterday [0] might be the fix? At least it fits Wadim's descripti= -on above=20 + [PATCH v4 1/7] regulator: rk808: Add rk808_reg_ops_ranges for LDO3 +from yesterday [0] might be the fix? At least it fits Wadim's description above but I haven't had time to test it yet. diff --git a/a/content_digest b/N1/content_digest index bc47fd0..0554d0b 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,50 +1,47 @@ "ref\0E1aukkg-0007km-6s@debutante\0" "ref\057205DC2.7070506@phytec.de\0" "ref\020160427135048.GQ3217@sirena.org.uk\0" - "From\0Heiko St\303\274bner <heiko@sntech.de>\0" + "ref\020160427135048.GQ3217-GFdadSzt00ze9xe1eoZjHA@public.gmane.org\0" + "From\0Heiko St\303\274bner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>\0" "Subject\0Re: Applied \"regulator: rk808: remove linear range definitions with a single range\" to the regulator tree\0" "Date\0Wed, 27 Apr 2016 15:56:56 +0200\0" - "To\0Mark Brown <broonie@kernel.org>\0" - "Cc\0Wadim Egorov <w.egorov@phytec.de>" - linux-rockchip@lists.infradead.org - mark.rutland@arm.com - devicetree@vger.kernel.org - a.zummo@towertech.it - pawel.moll@arm.com - rtc-linux@googlegroups.com - ijc+devicetree@hellion.org.uk - mturquette@baylibre.com - sboyd@codeaurora.org - linux-kernel@vger.kernel.org - robh+dt@kernel.org - lgirdwood@gmail.com - alexandre.belloni@free-electrons.com - dianders@chromium.org - galak@codeaurora.org - zyw@rock-chips.com - lee.jones@linaro.org - " linux-clk@vger.kernel.org\0" + "To\0Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>\0" + "Cc\0mark.rutland-5wv7dgnIgG8@public.gmane.org" + a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org + dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org + rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org + pawel.moll-5wv7dgnIgG8@public.gmane.org + devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org + ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org + sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org + linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org + linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org + robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org + alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org + galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org + zyw-TNX95d0MmH7DzftRWevZcw@public.gmane.org + Wadim Egorov <w.egorov-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org> + lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org + " linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\0" "\00:1\0" "b\0" "Am Mittwoch, 27. April 2016, 14:50:48 schrieb Mark Brown:\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=\n" - "\n" - "> > > rk3288-veyron devices with the bug below. Reverting this one patc=\n" - "h\n" - "> >=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" + "> > \n" "> > > results in the system booting again:\n" - "> > This is because I missed to add the correct ops for LDO_REG3 in thi=\n" - "s\n" + "> > This is because I missed to add the correct ops for LDO_REG3 in this\n" "> > patch.\n" - ">=20\n" + "> \n" "> Any ETA on a fix or should I revert?\n" "\n" "I guess\n" - "=09[PATCH v4 1/7] regulator: rk808: Add rk808_reg_ops_ranges for LDO3\n" - "from yesterday [0] might be the fix? At least it fits Wadim's descripti=\n" - "on above=20\n" + "\t[PATCH v4 1/7] regulator: rk808: Add rk808_reg_ops_ranges for LDO3\n" + "from yesterday [0] might be the fix? At least it fits Wadim's description above \n" "but I haven't had time to test it yet.\n" "\n" "\n" @@ -52,4 +49,4 @@ "\n" [0] https://patchwork.kernel.org/patch/8939741/ -fce509b825147295a68b6471561080b3661895c597fa978cfbb5236a68731ae2 +482449480d4d5bf336827220b1e9ff42a150f6190436b84d0d6b23abd27d11f4
diff --git a/a/1.txt b/N2/1.txt index 0d88e8e..0b0450a 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,25 +1,35 @@ Am Mittwoch, 27. April 2016, 14:50:48 schrieb Mark Brown: > 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= - -> > > rk3288-veyron devices with the bug below. Reverting this one patc= -h +> > 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 +> > > rk3288-veyron devices with the bug below. Reverting this one patch > >=20 > > > results in the system booting again: -> > This is because I missed to add the correct ops for LDO_REG3 in thi= -s +> > This is because I missed to add the correct ops for LDO_REG3 in this > > patch. >=20 > Any ETA on a fix or should I revert? I guess -=09[PATCH v4 1/7] regulator: rk808: Add rk808_reg_ops_ranges for LDO3 -from yesterday [0] might be the fix? At least it fits Wadim's descripti= -on above=20 + [PATCH v4 1/7] regulator: rk808: Add rk808_reg_ops_ranges for LDO3 +from yesterday [0] might be the fix? At least it fits Wadim's description a= +bove=20 but I haven't had time to test it yet. [0] https://patchwork.kernel.org/patch/8939741/ + +--=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 bc47fd0..70ad867 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -2,7 +2,7 @@ "ref\057205DC2.7070506@phytec.de\0" "ref\020160427135048.GQ3217@sirena.org.uk\0" "From\0Heiko St\303\274bner <heiko@sntech.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 15:56:56 +0200\0" "To\0Mark Brown <broonie@kernel.org>\0" "Cc\0Wadim Egorov <w.egorov@phytec.de>" @@ -28,28 +28,38 @@ "b\0" "Am Mittwoch, 27. April 2016, 14:50:48 schrieb Mark Brown:\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=\n" - "\n" - "> > > rk3288-veyron devices with the bug below. Reverting this one patc=\n" - "h\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\n" + "> > > rk3288-veyron devices with the bug below. Reverting this one patch\n" "> >=20\n" "> > > results in the system booting again:\n" - "> > This is because I missed to add the correct ops for LDO_REG3 in thi=\n" - "s\n" + "> > This is because I missed to add the correct ops for LDO_REG3 in this\n" "> > patch.\n" ">=20\n" "> Any ETA on a fix or should I revert?\n" "\n" "I guess\n" - "=09[PATCH v4 1/7] regulator: rk808: Add rk808_reg_ops_ranges for LDO3\n" - "from yesterday [0] might be the fix? At least it fits Wadim's descripti=\n" - "on above=20\n" + "\t[PATCH v4 1/7] regulator: rk808: Add rk808_reg_ops_ranges for LDO3\n" + "from yesterday [0] might be the fix? At least it fits Wadim's description a=\n" + "bove=20\n" "but I haven't had time to test it yet.\n" "\n" "\n" "\n" "\n" - [0] https://patchwork.kernel.org/patch/8939741/ + "[0] https://patchwork.kernel.org/patch/8939741/\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. -fce509b825147295a68b6471561080b3661895c597fa978cfbb5236a68731ae2 +f2e255a621d848458802fd08fe98c367f9aaf342e2a342391aa7aa5512845130
diff --git a/a/1.txt b/N3/1.txt index 0d88e8e..28bfe36 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -1,22 +1,18 @@ Am Mittwoch, 27. April 2016, 14:50:48 schrieb Mark Brown: > 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= - -> > > rk3288-veyron devices with the bug below. Reverting this one patc= -h -> >=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_REG3 in thi= -s +> > This is because I missed to add the correct ops for LDO_REG3 in this > > patch. ->=20 +> > Any ETA on a fix or should I revert? I guess -=09[PATCH v4 1/7] regulator: rk808: Add rk808_reg_ops_ranges for LDO3 -from yesterday [0] might be the fix? At least it fits Wadim's descripti= -on above=20 + [PATCH v4 1/7] regulator: rk808: Add rk808_reg_ops_ranges for LDO3 +from yesterday [0] might be the fix? At least it fits Wadim's description above but I haven't had time to test it yet. diff --git a/a/content_digest b/N3/content_digest index bc47fd0..5874c39 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -28,23 +28,19 @@ "b\0" "Am Mittwoch, 27. April 2016, 14:50:48 schrieb Mark Brown:\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=\n" - "\n" - "> > > rk3288-veyron devices with the bug below. Reverting this one patc=\n" - "h\n" - "> >=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" + "> > \n" "> > > results in the system booting again:\n" - "> > This is because I missed to add the correct ops for LDO_REG3 in thi=\n" - "s\n" + "> > This is because I missed to add the correct ops for LDO_REG3 in this\n" "> > patch.\n" - ">=20\n" + "> \n" "> Any ETA on a fix or should I revert?\n" "\n" "I guess\n" - "=09[PATCH v4 1/7] regulator: rk808: Add rk808_reg_ops_ranges for LDO3\n" - "from yesterday [0] might be the fix? At least it fits Wadim's descripti=\n" - "on above=20\n" + "\t[PATCH v4 1/7] regulator: rk808: Add rk808_reg_ops_ranges for LDO3\n" + "from yesterday [0] might be the fix? At least it fits Wadim's description above \n" "but I haven't had time to test it yet.\n" "\n" "\n" @@ -52,4 +48,4 @@ "\n" [0] https://patchwork.kernel.org/patch/8939741/ -fce509b825147295a68b6471561080b3661895c597fa978cfbb5236a68731ae2 +1692096dd51d8494c6a464dac562781132f208909f74021acd9abb1a9f22a3cc
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.