diff for duplicates of <20150602074004.GH3329@x1> diff --git a/a/1.txt b/N1/1.txt index 1f86062..55d4a5a 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -3,12 +3,9 @@ On Tue, 02 Jun 2015, Vaibhav Hiremath wrote: > >On Sat, 30 May 2015, Vaibhav Hiremath wrote: > > > >>RTC in pmic 88PM800 can run even the core is powered off, and user -> >>can set alarm in RTC. When the alarm is timed out, the PMIC will power = -up -> >>the core, and the whole system will boot up. And during PMIC driver pro= -be, -> >>it will read some register to find out whether this boot is caused by R= -TC +> >>can set alarm in RTC. When the alarm is timed out, the PMIC will power up +> >>the core, and the whole system will boot up. And during PMIC driver probe, +> >>it will read some register to find out whether this boot is caused by RTC > >>timeout or not, and pass on this information to the RTC driver. > >> > >>So we need rtc platform data to be existed in PMIC driver to pass this @@ -35,11 +32,10 @@ TC > >>+ * probed, it will read out some register to find out whether this > >>+ * boot is caused by RTC timeout or not, and it need pass this > >>+ * information to RTC driver. -> >>+ * So we need rtc platform data to be existed to pass this informatio= -n. +> >>+ * So we need rtc platform data to be existed to pass this information. > >>+ */ > >>+ if (!pdata->rtc) { -> >>+ pdata->rtc =3D devm_kzalloc(&client->dev, +> >>+ pdata->rtc = devm_kzalloc(&client->dev, > >>+ sizeof(*(pdata->rtc)), GFP_KERNEL); > >>+ if (!pdata->rtc) { > >>+ dev_err(&client->dev, @@ -51,13 +47,13 @@ n. > > > >Where is this memory first used? > > ->=20 +> > In the same file, look for field "rtc_wakeup". ->=20 +> > FYI, ->=20 +> > This field is used in two files, ->=20 +> > drivers/mfd/88pm800.c > and > drivers/rtc/rtc-88pm800.c [sets the "platform_data" field] @@ -73,21 +69,8 @@ struct pm80x_rtc_pdata { Is 'vrtc' even used? If so, where? ---=20 +-- Lee Jones Linaro STMicroelectronics Landing Team Lead -Linaro.org =E2=94=82 Open source software for ARM SoCs +Linaro.org ? Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog - ---=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 01be16d..5bf33f5 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,19 +2,10 @@ "ref\01432937962-4537-5-git-send-email-vaibhav.hiremath@linaro.org\0" "ref\020150601082200.GC3329@x1\0" "ref\0556D3A14.6050505@linaro.org\0" - "From\0Lee Jones <lee.jones@linaro.org>\0" - "Subject\0[rtc-linux] Re: [PATCH 4/4] mfd: 88pm800: allocate pdata->rtc if not allocated earlier\0" + "From\0lee.jones@linaro.org (Lee Jones)\0" + "Subject\0[PATCH 4/4] mfd: 88pm800: allocate pdata->rtc if not allocated earlier\0" "Date\0Tue, 2 Jun 2015 08:40:04 +0100\0" - "To\0Vaibhav Hiremath <vaibhav.hiremath@linaro.org>\0" - "Cc\0linux-arm-kernel@lists.infradead.org" - robh+dt@kernel.org - devicetree@vger.kernel.org - linux-kernel@vger.kernel.org - rtc-linux@googlegroups.com - sameo@linux.intel.com - a.zummo@towertech.it - alexandre.belloni@free-electrons.com - " Chao Xie <chao.xie@marvell.com>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On Tue, 02 Jun 2015, Vaibhav Hiremath wrote:\n" @@ -22,12 +13,9 @@ "> >On Sat, 30 May 2015, Vaibhav Hiremath wrote:\n" "> >\n" "> >>RTC in pmic 88PM800 can run even the core is powered off, and user\n" - "> >>can set alarm in RTC. When the alarm is timed out, the PMIC will power =\n" - "up\n" - "> >>the core, and the whole system will boot up. And during PMIC driver pro=\n" - "be,\n" - "> >>it will read some register to find out whether this boot is caused by R=\n" - "TC\n" + "> >>can set alarm in RTC. When the alarm is timed out, the PMIC will power up\n" + "> >>the core, and the whole system will boot up. And during PMIC driver probe,\n" + "> >>it will read some register to find out whether this boot is caused by RTC\n" "> >>timeout or not, and pass on this information to the RTC driver.\n" "> >>\n" "> >>So we need rtc platform data to be existed in PMIC driver to pass this\n" @@ -54,11 +42,10 @@ "> >>+\t * probed, it will read out some register to find out whether this\n" "> >>+\t * boot is caused by RTC timeout or not, and it need pass this\n" "> >>+\t * information to RTC driver.\n" - "> >>+\t * So we need rtc platform data to be existed to pass this informatio=\n" - "n.\n" + "> >>+\t * So we need rtc platform data to be existed to pass this information.\n" "> >>+\t */\n" "> >>+\tif (!pdata->rtc) {\n" - "> >>+\t\tpdata->rtc =3D devm_kzalloc(&client->dev,\n" + "> >>+\t\tpdata->rtc = devm_kzalloc(&client->dev,\n" "> >>+\t\t\t\t\t sizeof(*(pdata->rtc)), GFP_KERNEL);\n" "> >>+\t\tif (!pdata->rtc) {\n" "> >>+\t\t\tdev_err(&client->dev,\n" @@ -70,13 +57,13 @@ "> >\n" "> >Where is this memory first used?\n" "> >\n" - ">=20\n" + "> \n" "> In the same file, look for field \"rtc_wakeup\".\n" - ">=20\n" + "> \n" "> FYI,\n" - ">=20\n" + "> \n" "> This field is used in two files,\n" - ">=20\n" + "> \n" "> drivers/mfd/88pm800.c\n" "> and\n" "> drivers/rtc/rtc-88pm800.c\t[sets the \"platform_data\" field]\n" @@ -92,23 +79,10 @@ "\n" "Is 'vrtc' even used? If so, where?\n" "\n" - "--=20\n" + "-- \n" "Lee Jones\n" "Linaro STMicroelectronics Landing Team Lead\n" - "Linaro.org =E2=94=82 Open source software for ARM SoCs\n" - "Follow Linaro: Facebook | Twitter | Blog\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. + "Linaro.org ? Open source software for ARM SoCs\n" + Follow Linaro: Facebook | Twitter | Blog -97429f65d0d7391a90c4df6f4aa875e675bb1b11c2fd2411b4c54eef7dd0bbe9 +52ce79d98f87f848e81933e0201a0ca6a9494f7c7e658de7d10bfef2bd7540fc
diff --git a/a/1.txt b/N2/1.txt index 1f86062..09fc799 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -3,19 +3,16 @@ On Tue, 02 Jun 2015, Vaibhav Hiremath wrote: > >On Sat, 30 May 2015, Vaibhav Hiremath wrote: > > > >>RTC in pmic 88PM800 can run even the core is powered off, and user -> >>can set alarm in RTC. When the alarm is timed out, the PMIC will power = -up -> >>the core, and the whole system will boot up. And during PMIC driver pro= -be, -> >>it will read some register to find out whether this boot is caused by R= -TC +> >>can set alarm in RTC. When the alarm is timed out, the PMIC will power up +> >>the core, and the whole system will boot up. And during PMIC driver probe, +> >>it will read some register to find out whether this boot is caused by RTC > >>timeout or not, and pass on this information to the RTC driver. > >> > >>So we need rtc platform data to be existed in PMIC driver to pass this > >>information. > >> -> >>Signed-off-by: Chao Xie <chao.xie@marvell.com> -> >>Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@linaro.org> +> >>Signed-off-by: Chao Xie <chao.xie-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org> +> >>Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> > >>--- > >> drivers/mfd/88pm800.c | 19 +++++++++++++++++++ > >> 1 file changed, 19 insertions(+) @@ -35,11 +32,10 @@ TC > >>+ * probed, it will read out some register to find out whether this > >>+ * boot is caused by RTC timeout or not, and it need pass this > >>+ * information to RTC driver. -> >>+ * So we need rtc platform data to be existed to pass this informatio= -n. +> >>+ * So we need rtc platform data to be existed to pass this information. > >>+ */ > >>+ if (!pdata->rtc) { -> >>+ pdata->rtc =3D devm_kzalloc(&client->dev, +> >>+ pdata->rtc = devm_kzalloc(&client->dev, > >>+ sizeof(*(pdata->rtc)), GFP_KERNEL); > >>+ if (!pdata->rtc) { > >>+ dev_err(&client->dev, @@ -51,13 +47,13 @@ n. > > > >Where is this memory first used? > > ->=20 +> > In the same file, look for field "rtc_wakeup". ->=20 +> > FYI, ->=20 +> > This field is used in two files, ->=20 +> > drivers/mfd/88pm800.c > and > drivers/rtc/rtc-88pm800.c [sets the "platform_data" field] @@ -73,21 +69,12 @@ struct pm80x_rtc_pdata { Is 'vrtc' even used? If so, where? ---=20 +-- Lee Jones Linaro STMicroelectronics Landing Team Lead -Linaro.org =E2=94=82 Open source software for ARM SoCs +Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog - ---=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. +-- +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/N2/content_digest index 01be16d..0659596 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -2,19 +2,20 @@ "ref\01432937962-4537-5-git-send-email-vaibhav.hiremath@linaro.org\0" "ref\020150601082200.GC3329@x1\0" "ref\0556D3A14.6050505@linaro.org\0" - "From\0Lee Jones <lee.jones@linaro.org>\0" - "Subject\0[rtc-linux] Re: [PATCH 4/4] mfd: 88pm800: allocate pdata->rtc if not allocated earlier\0" + "ref\0556D3A14.6050505-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org\0" + "From\0Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>\0" + "Subject\0Re: [PATCH 4/4] mfd: 88pm800: allocate pdata->rtc if not allocated earlier\0" "Date\0Tue, 2 Jun 2015 08:40:04 +0100\0" - "To\0Vaibhav Hiremath <vaibhav.hiremath@linaro.org>\0" - "Cc\0linux-arm-kernel@lists.infradead.org" - robh+dt@kernel.org - devicetree@vger.kernel.org - linux-kernel@vger.kernel.org - rtc-linux@googlegroups.com - sameo@linux.intel.com - a.zummo@towertech.it - alexandre.belloni@free-electrons.com - " Chao Xie <chao.xie@marvell.com>\0" + "To\0Vaibhav Hiremath <vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>\0" + "Cc\0linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" + robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org + devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org + sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org + a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org + alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org + " Chao Xie <chao.xie-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>\0" "\00:1\0" "b\0" "On Tue, 02 Jun 2015, Vaibhav Hiremath wrote:\n" @@ -22,19 +23,16 @@ "> >On Sat, 30 May 2015, Vaibhav Hiremath wrote:\n" "> >\n" "> >>RTC in pmic 88PM800 can run even the core is powered off, and user\n" - "> >>can set alarm in RTC. When the alarm is timed out, the PMIC will power =\n" - "up\n" - "> >>the core, and the whole system will boot up. And during PMIC driver pro=\n" - "be,\n" - "> >>it will read some register to find out whether this boot is caused by R=\n" - "TC\n" + "> >>can set alarm in RTC. When the alarm is timed out, the PMIC will power up\n" + "> >>the core, and the whole system will boot up. And during PMIC driver probe,\n" + "> >>it will read some register to find out whether this boot is caused by RTC\n" "> >>timeout or not, and pass on this information to the RTC driver.\n" "> >>\n" "> >>So we need rtc platform data to be existed in PMIC driver to pass this\n" "> >>information.\n" "> >>\n" - "> >>Signed-off-by: Chao Xie <chao.xie@marvell.com>\n" - "> >>Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>\n" + "> >>Signed-off-by: Chao Xie <chao.xie-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>\n" + "> >>Signed-off-by: Vaibhav Hiremath <vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>\n" "> >>---\n" "> >> drivers/mfd/88pm800.c | 19 +++++++++++++++++++\n" "> >> 1 file changed, 19 insertions(+)\n" @@ -54,11 +52,10 @@ "> >>+\t * probed, it will read out some register to find out whether this\n" "> >>+\t * boot is caused by RTC timeout or not, and it need pass this\n" "> >>+\t * information to RTC driver.\n" - "> >>+\t * So we need rtc platform data to be existed to pass this informatio=\n" - "n.\n" + "> >>+\t * So we need rtc platform data to be existed to pass this information.\n" "> >>+\t */\n" "> >>+\tif (!pdata->rtc) {\n" - "> >>+\t\tpdata->rtc =3D devm_kzalloc(&client->dev,\n" + "> >>+\t\tpdata->rtc = devm_kzalloc(&client->dev,\n" "> >>+\t\t\t\t\t sizeof(*(pdata->rtc)), GFP_KERNEL);\n" "> >>+\t\tif (!pdata->rtc) {\n" "> >>+\t\t\tdev_err(&client->dev,\n" @@ -70,13 +67,13 @@ "> >\n" "> >Where is this memory first used?\n" "> >\n" - ">=20\n" + "> \n" "> In the same file, look for field \"rtc_wakeup\".\n" - ">=20\n" + "> \n" "> FYI,\n" - ">=20\n" + "> \n" "> This field is used in two files,\n" - ">=20\n" + "> \n" "> drivers/mfd/88pm800.c\n" "> and\n" "> drivers/rtc/rtc-88pm800.c\t[sets the \"platform_data\" field]\n" @@ -92,23 +89,14 @@ "\n" "Is 'vrtc' even used? If so, where?\n" "\n" - "--=20\n" + "-- \n" "Lee Jones\n" "Linaro STMicroelectronics Landing Team Lead\n" - "Linaro.org =E2=94=82 Open source software for ARM SoCs\n" + "Linaro.org \342\224\202 Open source software for ARM SoCs\n" "Follow Linaro: Facebook | Twitter | Blog\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. + "--\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 -97429f65d0d7391a90c4df6f4aa875e675bb1b11c2fd2411b4c54eef7dd0bbe9 +cb357d8f031e5eddb64b16c6430f1a97c16b4321de06168ae002727673d8d3fa
diff --git a/a/1.txt b/N3/1.txt index 1f86062..429cec9 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -3,12 +3,9 @@ On Tue, 02 Jun 2015, Vaibhav Hiremath wrote: > >On Sat, 30 May 2015, Vaibhav Hiremath wrote: > > > >>RTC in pmic 88PM800 can run even the core is powered off, and user -> >>can set alarm in RTC. When the alarm is timed out, the PMIC will power = -up -> >>the core, and the whole system will boot up. And during PMIC driver pro= -be, -> >>it will read some register to find out whether this boot is caused by R= -TC +> >>can set alarm in RTC. When the alarm is timed out, the PMIC will power up +> >>the core, and the whole system will boot up. And during PMIC driver probe, +> >>it will read some register to find out whether this boot is caused by RTC > >>timeout or not, and pass on this information to the RTC driver. > >> > >>So we need rtc platform data to be existed in PMIC driver to pass this @@ -35,11 +32,10 @@ TC > >>+ * probed, it will read out some register to find out whether this > >>+ * boot is caused by RTC timeout or not, and it need pass this > >>+ * information to RTC driver. -> >>+ * So we need rtc platform data to be existed to pass this informatio= -n. +> >>+ * So we need rtc platform data to be existed to pass this information. > >>+ */ > >>+ if (!pdata->rtc) { -> >>+ pdata->rtc =3D devm_kzalloc(&client->dev, +> >>+ pdata->rtc = devm_kzalloc(&client->dev, > >>+ sizeof(*(pdata->rtc)), GFP_KERNEL); > >>+ if (!pdata->rtc) { > >>+ dev_err(&client->dev, @@ -51,13 +47,13 @@ n. > > > >Where is this memory first used? > > ->=20 +> > In the same file, look for field "rtc_wakeup". ->=20 +> > FYI, ->=20 +> > This field is used in two files, ->=20 +> > drivers/mfd/88pm800.c > and > drivers/rtc/rtc-88pm800.c [sets the "platform_data" field] @@ -73,21 +69,8 @@ struct pm80x_rtc_pdata { Is 'vrtc' even used? If so, where? ---=20 +-- Lee Jones Linaro STMicroelectronics Landing Team Lead -Linaro.org =E2=94=82 Open source software for ARM SoCs +Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog - ---=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/N3/content_digest index 01be16d..ebbdf01 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -3,7 +3,7 @@ "ref\020150601082200.GC3329@x1\0" "ref\0556D3A14.6050505@linaro.org\0" "From\0Lee Jones <lee.jones@linaro.org>\0" - "Subject\0[rtc-linux] Re: [PATCH 4/4] mfd: 88pm800: allocate pdata->rtc if not allocated earlier\0" + "Subject\0Re: [PATCH 4/4] mfd: 88pm800: allocate pdata->rtc if not allocated earlier\0" "Date\0Tue, 2 Jun 2015 08:40:04 +0100\0" "To\0Vaibhav Hiremath <vaibhav.hiremath@linaro.org>\0" "Cc\0linux-arm-kernel@lists.infradead.org" @@ -22,12 +22,9 @@ "> >On Sat, 30 May 2015, Vaibhav Hiremath wrote:\n" "> >\n" "> >>RTC in pmic 88PM800 can run even the core is powered off, and user\n" - "> >>can set alarm in RTC. When the alarm is timed out, the PMIC will power =\n" - "up\n" - "> >>the core, and the whole system will boot up. And during PMIC driver pro=\n" - "be,\n" - "> >>it will read some register to find out whether this boot is caused by R=\n" - "TC\n" + "> >>can set alarm in RTC. When the alarm is timed out, the PMIC will power up\n" + "> >>the core, and the whole system will boot up. And during PMIC driver probe,\n" + "> >>it will read some register to find out whether this boot is caused by RTC\n" "> >>timeout or not, and pass on this information to the RTC driver.\n" "> >>\n" "> >>So we need rtc platform data to be existed in PMIC driver to pass this\n" @@ -54,11 +51,10 @@ "> >>+\t * probed, it will read out some register to find out whether this\n" "> >>+\t * boot is caused by RTC timeout or not, and it need pass this\n" "> >>+\t * information to RTC driver.\n" - "> >>+\t * So we need rtc platform data to be existed to pass this informatio=\n" - "n.\n" + "> >>+\t * So we need rtc platform data to be existed to pass this information.\n" "> >>+\t */\n" "> >>+\tif (!pdata->rtc) {\n" - "> >>+\t\tpdata->rtc =3D devm_kzalloc(&client->dev,\n" + "> >>+\t\tpdata->rtc = devm_kzalloc(&client->dev,\n" "> >>+\t\t\t\t\t sizeof(*(pdata->rtc)), GFP_KERNEL);\n" "> >>+\t\tif (!pdata->rtc) {\n" "> >>+\t\t\tdev_err(&client->dev,\n" @@ -70,13 +66,13 @@ "> >\n" "> >Where is this memory first used?\n" "> >\n" - ">=20\n" + "> \n" "> In the same file, look for field \"rtc_wakeup\".\n" - ">=20\n" + "> \n" "> FYI,\n" - ">=20\n" + "> \n" "> This field is used in two files,\n" - ">=20\n" + "> \n" "> drivers/mfd/88pm800.c\n" "> and\n" "> drivers/rtc/rtc-88pm800.c\t[sets the \"platform_data\" field]\n" @@ -92,23 +88,10 @@ "\n" "Is 'vrtc' even used? If so, where?\n" "\n" - "--=20\n" + "-- \n" "Lee Jones\n" "Linaro STMicroelectronics Landing Team Lead\n" - "Linaro.org =E2=94=82 Open source software for ARM SoCs\n" - "Follow Linaro: Facebook | Twitter | Blog\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. + "Linaro.org \342\224\202 Open source software for ARM SoCs\n" + Follow Linaro: Facebook | Twitter | Blog -97429f65d0d7391a90c4df6f4aa875e675bb1b11c2fd2411b4c54eef7dd0bbe9 +6369dc7254f848cf761ca6bee119966a50ca5ac6b459c354b1c23aa67dceb32e
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.