diff for duplicates of <571F2AFE.2020006@phytec.de> diff --git a/a/1.txt b/N1/1.txt index 25d44f6..0964bca 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -25,3 +25,7 @@ On 26.04.2016 10:17, Heiko Stübner wrote: > > Heiko I will drop the first patch and send a v4 later +-- +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 b2028ee..b288cdf 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,29 +2,29 @@ "ref\020160425173911.GQ3217@sirena.org.uk\0" "ref\0571F1CB4.10200@phytec.de\0" "ref\02669414.IKg01zC8vG@diego\0" - "From\0Wadim Egorov <w.egorov@phytec.de>\0" + "From\0Wadim Egorov <w.egorov-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>\0" "Subject\0Re: [PATCH v3 4/8] regulator: rk808: Migrate to regulator core's simplified DT parsing code\0" "Date\0Tue, 26 Apr 2016 10:46:54 +0200\0" - "To\0Heiko St\303\274bner <heiko@sntech.de>\0" - "Cc\0Mark Brown <broonie@kernel.org>" - linux-kernel@vger.kernel.org - linux-clk@vger.kernel.org - rtc-linux@googlegroups.com - devicetree@vger.kernel.org - linux-rockchip@lists.infradead.org - robh+dt@kernel.org - pawel.moll@arm.com - mark.rutland@arm.com - ijc+devicetree@hellion.org.uk - galak@codeaurora.org - mturquette@baylibre.com - sboyd@codeaurora.org - lee.jones@linaro.org - lgirdwood@gmail.com - a.zummo@towertech.it - alexandre.belloni@free-electrons.com - dianders@chromium.org - " zyw@rock-chips.com\0" + "To\0Heiko St\303\274bner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>\0" + "Cc\0Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>" + linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org + devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org + robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org + pawel.moll-5wv7dgnIgG8@public.gmane.org + mark.rutland-5wv7dgnIgG8@public.gmane.org + ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org + galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org + mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org + sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org + lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org + lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org + a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org + alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org + dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org + " zyw-TNX95d0MmH7DzftRWevZcw@public.gmane.org\0" "\00:1\0" "b\0" "\n" @@ -53,6 +53,10 @@ ">\n" ">\n" "> Heiko\n" - I will drop the first patch and send a v4 later + "I will drop the first patch and send a v4 later\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 -38eee107cb023fee324306fc3a9e96ee546267deaeba0efb36cc48bba31f0f7d +381afb452de0767bc815369ed1975d2311cd164a2256d687f0574a53e93792c3
diff --git a/a/1.txt b/N2/1.txt index 25d44f6..5520b99 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,6 +1,6 @@ -On 26.04.2016 10:17, Heiko Stübner wrote: +On 26.04.2016 10:17, Heiko St=C3=BCbner wrote: > Am Dienstag, 26. April 2016, 09:45:56 schrieb Wadim Egorov: >> On 25.04.2016 19:39, Mark Brown wrote: >>> On Mon, Apr 25, 2016 at 03:20:44PM +0200, Wadim Egorov wrote: @@ -10,18 +10,37 @@ On 26.04.2016 10:17, Heiko Stübner wrote: >>> This doesn't apply against current code, please check and resend. >> Hm, for me all patches apply to the current code. >> This patch depends on the first rename patch. Maybe this is the problem? -> which is the reason why renaming stuff makes everything just more complicated -> without providing additional value ;-) +> which is the reason why renaming stuff makes everything just more complic= +ated=20 +> without providing additional value ;-)=20 > -> The first patch would go through the mfd-tree (if accepted by Lee and Acked by -> the other involved subsystem maintainers) which would then need a stable -> branch merged into the regulator tree - or after the first patch goes in you +> The first patch would go through the mfd-tree (if accepted by Lee and Ack= +ed by=20 +> the other involved subsystem maintainers) which would then need a stable= +=20 +> branch merged into the regulator tree - or after the first patch goes in = +you=20 > simply wait for a kernel release. > -> Normally I would expect the reasonable kernel developer to be able to simply -> read code, kconfig, docs stating the drivers being for rk808 and rk818 without +> Normally I would expect the reasonable kernel developer to be able to sim= +ply=20 +> read code, kconfig, docs stating the drivers being for rk808 and rk818 wi= +thout=20 > getting "confused" by some structs mentioning the rk808. > > > Heiko I will drop the first patch and send a v4 later + +--=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 b2028ee..452b0a3 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -3,7 +3,7 @@ "ref\0571F1CB4.10200@phytec.de\0" "ref\02669414.IKg01zC8vG@diego\0" "From\0Wadim Egorov <w.egorov@phytec.de>\0" - "Subject\0Re: [PATCH v3 4/8] regulator: rk808: Migrate to regulator core's simplified DT parsing code\0" + "Subject\0[rtc-linux] Re: [PATCH v3 4/8] regulator: rk808: Migrate to regulator core's simplified DT parsing code\0" "Date\0Tue, 26 Apr 2016 10:46:54 +0200\0" "To\0Heiko St\303\274bner <heiko@sntech.de>\0" "Cc\0Mark Brown <broonie@kernel.org>" @@ -29,7 +29,7 @@ "b\0" "\n" "\n" - "On 26.04.2016 10:17, Heiko St\303\274bner wrote:\n" + "On 26.04.2016 10:17, Heiko St=C3=BCbner wrote:\n" "> Am Dienstag, 26. April 2016, 09:45:56 schrieb Wadim Egorov:\n" ">> On 25.04.2016 19:39, Mark Brown wrote:\n" ">>> On Mon, Apr 25, 2016 at 03:20:44PM +0200, Wadim Egorov wrote:\n" @@ -39,20 +39,39 @@ ">>> This doesn't apply against current code, please check and resend.\n" ">> Hm, for me all patches apply to the current code.\n" ">> This patch depends on the first rename patch. Maybe this is the problem?\n" - "> which is the reason why renaming stuff makes everything just more complicated \n" - "> without providing additional value ;-) \n" + "> which is the reason why renaming stuff makes everything just more complic=\n" + "ated=20\n" + "> without providing additional value ;-)=20\n" ">\n" - "> The first patch would go through the mfd-tree (if accepted by Lee and Acked by \n" - "> the other involved subsystem maintainers) which would then need a stable \n" - "> branch merged into the regulator tree - or after the first patch goes in you \n" + "> The first patch would go through the mfd-tree (if accepted by Lee and Ack=\n" + "ed by=20\n" + "> the other involved subsystem maintainers) which would then need a stable=\n" + "=20\n" + "> branch merged into the regulator tree - or after the first patch goes in =\n" + "you=20\n" "> simply wait for a kernel release.\n" ">\n" - "> Normally I would expect the reasonable kernel developer to be able to simply \n" - "> read code, kconfig, docs stating the drivers being for rk808 and rk818 without \n" + "> Normally I would expect the reasonable kernel developer to be able to sim=\n" + "ply=20\n" + "> read code, kconfig, docs stating the drivers being for rk808 and rk818 wi=\n" + "thout=20\n" "> getting \"confused\" by some structs mentioning the rk808.\n" ">\n" ">\n" "> Heiko\n" - I will drop the first patch and send a v4 later + "I will drop the first patch and send a v4 later\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. -38eee107cb023fee324306fc3a9e96ee546267deaeba0efb36cc48bba31f0f7d +6a681408acb7426fb4062fe9266af330dd620867c39fd72691310e2e4e44d8bf
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.