diff for duplicates of <20150917123138.GG4287@piout.net> diff --git a/a/1.txt b/N1/1.txt index b29fa40..0c8ac06 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,50 +1,30 @@ 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 [=20 -> > 1.078985 ] rtc-hym8563 1-0051: no valid clock/calendar values availab= -le [ +> > [ 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 -> >=20 +> > > > 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) ->=20 -> hmm, not setting a false date was actually intentional when I did the dri= -ver. ->=20 -> In my mind it is better to shout and keep programs from using wrong value= -s=20 -> than to set some arbitary date and let programs silently use this wrong v= -alue. ->=20 +> +> 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 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. ---=20 +-- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com - ---=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 23bd032..cc36b8c 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,7 +2,7 @@ "ref\01442486368-1912-1-git-send-email-zhengxing@rock-chips.com\0" "ref\03439697.Ymf0XB1EzX@diego\0" "From\0Alexandre Belloni <alexandre.belloni@free-electrons.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 14:31:38 +0200\0" "To\0Heiko St\303\274bner <heiko@sntech.de>\0" "Cc\0Xing Zheng <zhengxing@rock-chips.com>" @@ -13,53 +13,33 @@ "b\0" "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 [=20\n" - "> > 1.078985 ] rtc-hym8563 1-0051: no valid clock/calendar values availab=\n" - "le [\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" - "> >=20\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" - ">=20\n" - "> hmm, not setting a false date was actually intentional when I did the dri=\n" - "ver.\n" - ">=20\n" - "> In my mind it is better to shout and keep programs from using wrong value=\n" - "s=20\n" - "> than to set some arbitary date and let programs silently use this wrong v=\n" - "alue.\n" - ">=20\n" + "> \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 values \n" + "> than to set some arbitary date and let programs silently use this wrong value.\n" + "> \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" - "--=20\n" + "-- \n" "Alexandre Belloni, Free Electrons\n" "Embedded Linux, Kernel and Android engineering\n" - "http://free-electrons.com\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. + http://free-electrons.com -8bb65fb6674c4e461353944b19af8c96638ed18f33f3e1e5e94b022fed5dfcb5 +06e42386c4f899483119b8a5f3423e47bc97db77bd4118e041f5843f3145447b
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.