[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <OFC41C6D99.FB9C3A21-ON48257E59.0005C8A9-48257E59.00073A3F@zte.com.cn>
Date: Wed, 3 Jun 2015 09:19:01 +0800
From: pang.xunlei@....com.cn
To: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
Cc: Alessandro Zummo <a.zummo@...ertech.it>,
Arnd Bergmann <arnd@...db.de>,
John Stultz <john.stultz@...aro.org>,
linux-kernel@...r.kernel.org, Xunlei Pang <pang.xunlei@...aro.org>,
rtc-linux@...glegroups.com
Subject: Re: [PATCH v2 1/4] drivers/rtc/pcf8563: Replace deprecated rtc_time_to_tm() and
rtc_tm_to_time()
Hi Alexandre,
Alexandre Belloni <alexandre.belloni@...e-electrons.com> wrote 2015-06-03
AM 12:41:25:
> Re: [PATCH v2 1/4] drivers/rtc/pcf8563: Replace deprecated
> rtc_time_to_tm() and rtc_tm_to_time()
>
> On 03/06/2015 at 00:23:40 +0900, pang.xunlei@....com.cn wrote :
> > Apologies for the spamming, please ignore all those former 27 pending
> > patches.
> >
> > I'll re-organize them with a cover letter, will resend them as new
ones
> > tomorrow.
> >
>
> 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
> 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
clocksource
> 431649 [1/5] drivers/rtc/interface.c: Update code to use y2038-safe
> time interfaces
> 431650 [2/5] drivers/rtc/rtc-dev.c: Update code to use y2038-safe
> time interfaces
> 431798 [v2,3/3] time: clocksource: Add a comment to
> CLOCK_SOURCE_SUSPEND_NONSTOP
> 434592 [v3,1/2] time: Don't bother to run rtc_resume() for the
> nonstop clocksource
> 448780 [5/8] ARM: tegra: clock: Provide y2038-safe
> tegra_read_persistent_clock() replacement
> 448782 [6/8] ARM: time: Provide read_boot_clock64() and
> read_persistent_clock64()
> 448781 [7/8] s390: time: Provide read_boot_clock64() and
> 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.
>
> You just sent those so I guess I still have to review them:
> 477947 [RESEND,1/3] drivers/rtc/pcf8563: Replace deprecated
> rtc_time_to_tm() and rtc_tm_to_time()
> 477949 [RESEND,2/3] drivers/rtc/isl1208: Replace deprecated
rtc_tm_to_time()
> 477948 [RESEND,3/3] drivers/rtc/sunxi: Replace deprecated
rtc_tm_to_time()
Patch series below is about replacing deprecated
rtc_tm_to_time()/rtc_time_to_tm()
mostly in rtc drivers with their y2038-safe substitutes
rtc_tm_to_time64()/
rtc_time64_to_tm() which were merged into upstream last year.
> 479350 [v2,1/4] drivers/rtc/pcf8563: Replace deprecated
> 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
remove
it if can(mainly for rtc-related persistent clock).
> 479360 [v2,1/4] NTP: rtc: Add CONFIG_RTC_SYSTOHC_DEVICE for NTP
> synchronization
> 479359 [v2,2/4] sparc: time: Replace update_persistent_clock() with
> 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
>
> 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 (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists