Hi Alexandre,

Alexandre Belloni [off-list ref] wrote 2015-06-03=
=20
AM 12:41:25:

Re: [PATCH v2 1/4] drivers/rtc/pcf8563: Replace deprecated=20
rtc_time_to_tm() and rtc_tm_to_time()
=20
On 03/06/2015 at 00:23:40 +0900, pang.xunlei@zte.com.cn wrote :

quoted

Apologies for the spamming, please ignore all those former 27 pending=

=20

quoted

patches.
=20
I'll re-organize them with a cover letter, will resend them as new=20

ones=20

quoted

tomorrow.
=20

=20
Or maybe, instead of resending, you can give me the status of those
patches:

Ok, I'll use a cover letter in future ones like so.

415468 [RFC,2/4] rtc: Convert rtc_class_ops.set_mmss() to use time64_t
415470 [RFC,3/4] rtc/lib: Provide interfaces to map between 32bit=20
hardware and 64bit time
428475 [RFC,v2,2/9] time: Provide y2106 safe get_seconds() replacement
431162 [1/3] time: Don't bother to run rtc_resume() for nonstop=20

clocksource

431649 [1/5] drivers/rtc/interface.c: Update code to use y2038-safe=20
time interfaces
431650 [2/5] drivers/rtc/rtc-dev.c: Update code to use y2038-safe=20
time interfaces
431798 [v2,3/3] time: clocksource: Add a comment to=20
CLOCK_SOURCE_SUSPEND_NONSTOP
434592 [v3,1/2] time: Don't bother to run rtc_resume() for the=20
nonstop clocksource
448780 [5/8] ARM: tegra: clock: Provide y2038-safe=20
tegra_read_persistent_clock() replacement
448782 [6/8] ARM: time: Provide read_boot_clock64() and=20
read_persistent_clock64()
448781 [7/8] s390: time: Provide read_boot_clock64() and=20
read_persistent_clock64()
448783 [8/8] time: Remove read_boot_clock()

The above had already been merged into upstream, at least I can see them
in tip/master now.

=20
You just sent those so I guess I still have to review them:
477947 [RESEND,1/3] drivers/rtc/pcf8563: Replace deprecated=20
rtc_time_to_tm() and rtc_tm_to_time()
477949 [RESEND,2/3] drivers/rtc/isl1208: Replace deprecated=20

rtc_tm_to_time()

477948 [RESEND,3/3] drivers/rtc/sunxi: Replace deprecated=20

rtc_tm_to_time()


Patch series below is about replacing deprecated=20
rtc_tm_to_time()/rtc_time_to_tm()
mostly in rtc drivers with their y2038-safe substitutes=20
rtc_tm_to_time64()/
rtc_time64_to_tm() which were merged into upstream last year.

479350 [v2,1/4] drivers/rtc/pcf8563: Replace deprecated=20
rtc_time_to_tm() and rtc_tm_to_time()
479348 [v2,2/4] rtc/lib: Introduce rtc_tm_subtract() helper function
479351 [v2,3/4] drivers/rtc/isl1208: Replace deprecated rtc_tm_to_time()
479349 [v2,4/4] drivers/rtc/sunxi: Replace deprecated rtc_tm_to_time()

And in the following one, I want to replace all the xxx_persistent_clock()
architecture implementations with xxx_persistent_clock64() or simply=20
remove
it if can(mainly for rtc-related persistent clock).

479360 [v2,1/4] NTP: rtc: Add CONFIG_RTC_SYSTOHC_DEVICE for NTP=20
synchronization
479359 [v2,2/4] sparc: time: Replace update_persistent_clock() with=20
CONFIG_RTC_SYSTOHC
479358 [v2,3/4] drivers/rtc/interface.c: Remove rtc_set_mmss()
479357 [v2,4/4] cris: time: Cleanup of persistent clock stuff
=20
Many thanks for your work.

I think you can only review the two v2 series :-)

-Xunlei

--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (an=
d any attachment transmitted herewith) is privileged and confidential and i=
s intended for the exclusive use of the addressee(s).  If you are not an in=
tended recipient, any disclosure, reproduction, distribution or other disse=
mination or use of the information contained is strictly prohibited.  If yo=
u have received this mail in error, please delete it and notify us immediat=
ely.
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (an=
d any attachment transmitted herewith) is privileged and confidential and i=
s intended for the exclusive use of the addressee(s).  If you are not an in=
tended recipient, any disclosure, reproduction, distribution or other disse=
mination or use of the information contained is strictly prohibited.  If yo=
u have received this mail in error, please delete it and notify us immediat=
ely.

--=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.