diff for duplicates of <55FAB5B6.3010605@rock-chips.com> diff --git a/a/1.txt b/N1/1.txt index 8f64814..fd302d2 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,47 +1,27 @@ -On 2015=E5=B9=B409=E6=9C=8817=E6=97=A5 20:31, Alexandre Belloni wrote: +On 2015年09月17日 20:31, Alexandre Belloni wrote: > Hi, > -> On 17/09/2015 at 14:07:47 +0200, Heiko St=C3=BCbner wrote : +> On 17/09/2015 at 14:07:47 +0200, Heiko Stübner wrote : >> Am Donnerstag, 17. September 2015, 18:39:28 schrieb Xing Zheng: >>> The rtc hym8563 maybe failed to register if first startup or rtc >>> powerdown: ->>> [ 0.988540 ] rtc-hym8563 1-0051: no valid clock/calendar values avai= -lable ->>> [ 0.995642 ] rtc-hym8563 1-0051: rtc core: registered hym8563 as rtc= -0 [ ->>> 1.078985 ] rtc-hym8563 1-0051: no valid clock/calendar values availa= -ble [ +>>> [ 0.988540 ] rtc-hym8563 1-0051: no valid clock/calendar values available +>>> [ 0.995642 ] rtc-hym8563 1-0051: rtc core: registered hym8563 as rtc0 [ +>>> 1.078985 ] rtc-hym8563 1-0051: no valid clock/calendar values available [ >>> 1.085698 ] rtc-hym8563 1-0051: hctosys: unable to read the hardware >>> clock >>> >>> We can set initial time for rtc and register it: ->>> [ 0.995678 ] rtc-hym8563 1-0051: rtc core: registered hym8563 as rtc= -0 +>>> [ 0.995678 ] rtc-hym8563 1-0051: rtc core: registered hym8563 as rtc0 >>> [ 1.080313 ] rtc-hym8563 1-0051: setting system clock to 2000-01-01 >>> 00:02:00 UTC (946684920) ->> hmm, not setting a false date was actually intentional when I did the dr= -iver. +>> hmm, not setting a false date was actually intentional when I did the driver. >> ->> In my mind it is better to shout and keep programs from using wrong valu= -es ->> than to set some arbitary date and let programs silently use this wrong = -value. +>> In my mind it is better to shout and keep programs from using wrong values +>> than to set some arbitary date and let programs silently use this wrong value. >> > Indeed, I find it worse to set a wrong value instead of returning an > error. Userspace has to define its policy when reading the time fails. > OK, I got it, this patch will be abandoned at next version. Thanks. - ---=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 c821889..9e8488e 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,7 +3,7 @@ "ref\03439697.Ymf0XB1EzX@diego\0" "ref\020150917123138.GG4287@piout.net\0" "From\0Xing Zheng <zhengxing@rock-chips.com>\0" - "Subject\0[rtc-linux] Re: [PATCH v2 9/9] rtc: hym8563: make sure hym8563 can be normal work\0" + "Subject\0Re: [PATCH v2 9/9] rtc: hym8563: make sure hym8563 can be normal work\0" "Date\0Thu, 17 Sep 2015 20:44:38 +0800\0" "To\0Alexandre Belloni <alexandre.belloni@free-electrons.com>\0" "Cc\0Heiko St\303\274bner <heiko@sntech.de>" @@ -12,52 +12,32 @@ " linux-kernel@vger.kernel.org\0" "\00:1\0" "b\0" - "On 2015=E5=B9=B409=E6=9C=8817=E6=97=A5 20:31, Alexandre Belloni wrote:\n" + "On 2015\345\271\26409\346\234\21017\346\227\245 20:31, Alexandre Belloni wrote:\n" "> Hi,\n" ">\n" - "> On 17/09/2015 at 14:07:47 +0200, Heiko St=C3=BCbner wrote :\n" + "> On 17/09/2015 at 14:07:47 +0200, Heiko St\303\274bner wrote :\n" ">> Am Donnerstag, 17. September 2015, 18:39:28 schrieb Xing Zheng:\n" ">>> The rtc hym8563 maybe failed to register if first startup or rtc\n" ">>> powerdown:\n" - ">>> [ 0.988540 ] rtc-hym8563 1-0051: no valid clock/calendar values avai=\n" - "lable\n" - ">>> [ 0.995642 ] rtc-hym8563 1-0051: rtc core: registered hym8563 as rtc=\n" - "0 [\n" - ">>> 1.078985 ] rtc-hym8563 1-0051: no valid clock/calendar values availa=\n" - "ble [\n" + ">>> [ 0.988540 ] rtc-hym8563 1-0051: no valid clock/calendar values available\n" + ">>> [ 0.995642 ] rtc-hym8563 1-0051: rtc core: registered hym8563 as rtc0 [\n" + ">>> 1.078985 ] rtc-hym8563 1-0051: no valid clock/calendar values available [\n" ">>> 1.085698 ] rtc-hym8563 1-0051: hctosys: unable to read the hardware\n" ">>> clock\n" ">>>\n" ">>> We can set initial time for rtc and register it:\n" - ">>> [ 0.995678 ] rtc-hym8563 1-0051: rtc core: registered hym8563 as rtc=\n" - "0\n" + ">>> [ 0.995678 ] rtc-hym8563 1-0051: rtc core: registered hym8563 as rtc0\n" ">>> [ 1.080313 ] rtc-hym8563 1-0051: setting system clock to 2000-01-01\n" ">>> 00:02:00 UTC (946684920)\n" - ">> hmm, not setting a false date was actually intentional when I did the dr=\n" - "iver.\n" + ">> hmm, not setting a false date was actually intentional when I did the driver.\n" ">>\n" - ">> In my mind it is better to shout and keep programs from using wrong valu=\n" - "es\n" - ">> than to set some arbitary date and let programs silently use this wrong =\n" - "value.\n" + ">> In my mind it is better to shout and keep programs from using wrong values\n" + ">> than to set some arbitary date and let programs silently use this wrong value.\n" ">>\n" "> Indeed, I find it worse to set a wrong value instead of returning an\n" "> error. Userspace has to define its policy when reading the time fails.\n" ">\n" "OK, I got it, this patch will be abandoned at next version.\n" - "Thanks.\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. + Thanks. -c20ce7bdb08266d635310b53381da50a03859d94ec50194a5460abad25f184a9 +dffdc23138742ba575f9ec8260ceae8d110156f1f32b67bb3de45a6e0101b1a9
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.