From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [PATCH 00/51] rtc: stop using rtc deprecated functions Date: Tue, 20 Jun 2017 14:10:11 +0200 Message-ID: <20170620121011.GA13221@amd> References: <1497951359-13334-1-git-send-email-benjamin.gaignard@linaro.org> <20170620100348.zh4ygvjjgnhxvmvl@piout.net> Reply-To: rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" Return-path: Sender: rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Content-Disposition: inline In-Reply-To: <20170620100348.zh4ygvjjgnhxvmvl-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org> List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , To: Alexandre Belloni Cc: Benjamin Gaignard , linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org, adi-buildroot-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Alessandro Zummo , Gregory Clement , Ingo Molnar , Jason Cooper , John Stultz , linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Linus Walleij , Michael Chan , netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org, Sebastian Hesselbarth , Support Opensource , Thomas Gleixner , x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, Baruch Siach , Hans Ulli Kroll , Vladimir Zapolskiy , Sylvain Lemieux , Barry Song List-Id: linux-tegra@vger.kernel.org --UugvWAfsgieZRqgk Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline On Tue 2017-06-20 12:03:48, Alexandre Belloni wrote: > On 20/06/2017 at 11:35:08 +0200, Benjamin Gaignard wrote: > > rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they > > rely on 32bits variables and that will make rtc break in y2038/2016. > > Please don't, because this hide the fact that the hardware will not > handle dates in y2038 anyway and as pointed by Russell a few month ago, > rtc_time_to_tm will be able to catch it but the 64 bit version will > silently ignore it. Reference? Because rtc on PCs stores date in binary coded decimal, so it is likely to break in 2100, not 2038... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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. --- 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 email to rtc-linux+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit https://groups.google.com/d/optout. --UugvWAfsgieZRqgk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAllJEKMACgkQMOfwapXb+vLe9wCgu9cyUI440c/59xBQrQRexyjC q9UAnRKqRfLSYD/VIlYozWlk+CWfUWFP =o49/ -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751774AbdFTMKQ (ORCPT ); Tue, 20 Jun 2017 08:10:16 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:60773 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751105AbdFTMKO (ORCPT ); Tue, 20 Jun 2017 08:10:14 -0400 Date: Tue, 20 Jun 2017 14:10:11 +0200 From: Pavel Machek To: Alexandre Belloni Cc: Benjamin Gaignard , linaro-kernel@lists.linaro.org, adi-buildroot-devel@lists.sourceforge.net, Alessandro Zummo , Gregory Clement , Ingo Molnar , Jason Cooper , John Stultz , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Linus Walleij , Michael Chan , netdev@vger.kernel.org, rtc-linux@googlegroups.com, Sebastian Hesselbarth , Support Opensource , Thomas Gleixner , x86@kernel.org, Baruch Siach , Hans Ulli Kroll , Vladimir Zapolskiy , Sylvain Lemieux , Barry Song , Maxime Ripard , Chen-Yu Tsai , Thierry Reding , Jonathan Hunter , linux-tegra@vger.kernel.org, patches@opensource.wolfsonmicro.com, "Rafael J. Wysocki" , Len Brown , linux-pm@vger.kernel.org Subject: Re: [PATCH 00/51] rtc: stop using rtc deprecated functions Message-ID: <20170620121011.GA13221@amd> References: <1497951359-13334-1-git-send-email-benjamin.gaignard@linaro.org> <20170620100348.zh4ygvjjgnhxvmvl@piout.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline In-Reply-To: <20170620100348.zh4ygvjjgnhxvmvl@piout.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue 2017-06-20 12:03:48, Alexandre Belloni wrote: > On 20/06/2017 at 11:35:08 +0200, Benjamin Gaignard wrote: > > rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they > > rely on 32bits variables and that will make rtc break in y2038/2016. >=20 > Please don't, because this hide the fact that the hardware will not > handle dates in y2038 anyway and as pointed by Russell a few month ago, > rtc_time_to_tm will be able to catch it but the 64 bit version will > silently ignore it. Reference? Because rtc on PCs stores date in binary coded decimal, so it is likely to break in 2100, not 2038... Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --UugvWAfsgieZRqgk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAllJEKMACgkQMOfwapXb+vLe9wCgu9cyUI440c/59xBQrQRexyjC q9UAnRKqRfLSYD/VIlYozWlk+CWfUWFP =o49/ -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Sender: rtc-linux@googlegroups.com Received: from atrey.karlin.mff.cuni.cz (atrey.karlin.mff.cuni.cz. [195.113.26.193]) by gmr-mx.google.com with ESMTPS id v127si3808765wmd.4.2017.06.20.05.10.12 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Jun 2017 05:10:12 -0700 (PDT) Date: Tue, 20 Jun 2017 14:10:11 +0200 From: Pavel Machek To: Alexandre Belloni Cc: Benjamin Gaignard , linaro-kernel@lists.linaro.org, adi-buildroot-devel@lists.sourceforge.net, Alessandro Zummo , Gregory Clement , Ingo Molnar , Jason Cooper , John Stultz , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Linus Walleij , Michael Chan , netdev@vger.kernel.org, rtc-linux@googlegroups.com, Sebastian Hesselbarth , Support Opensource , Thomas Gleixner , x86@kernel.org, Baruch Siach , Hans Ulli Kroll , Vladimir Zapolskiy , Sylvain Lemieux , Barry Song , Maxime Ripard , Chen-Yu Tsai , Thierry Reding , Jonathan Hunter , linux-tegra@vger.kernel.org, patches@opensource.wolfsonmicro.com, "Rafael J. Wysocki" , Len Brown , linux-pm@vger.kernel.org Subject: [rtc-linux] Re: [PATCH 00/51] rtc: stop using rtc deprecated functions Message-ID: <20170620121011.GA13221@amd> References: <1497951359-13334-1-git-send-email-benjamin.gaignard@linaro.org> <20170620100348.zh4ygvjjgnhxvmvl@piout.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" In-Reply-To: <20170620100348.zh4ygvjjgnhxvmvl@piout.net> Reply-To: rtc-linux@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , --UugvWAfsgieZRqgk Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline On Tue 2017-06-20 12:03:48, Alexandre Belloni wrote: > On 20/06/2017 at 11:35:08 +0200, Benjamin Gaignard wrote: > > rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they > > rely on 32bits variables and that will make rtc break in y2038/2016. > > Please don't, because this hide the fact that the hardware will not > handle dates in y2038 anyway and as pointed by Russell a few month ago, > rtc_time_to_tm will be able to catch it but the 64 bit version will > silently ignore it. Reference? Because rtc on PCs stores date in binary coded decimal, so it is likely to break in 2100, not 2038... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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. --- 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 email to rtc-linux+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout. --UugvWAfsgieZRqgk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAllJEKMACgkQMOfwapXb+vLe9wCgu9cyUI440c/59xBQrQRexyjC q9UAnRKqRfLSYD/VIlYozWlk+CWfUWFP =o49/ -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [PATCH 00/51] rtc: stop using rtc deprecated functions Date: Tue, 20 Jun 2017 14:10:11 +0200 Message-ID: <20170620121011.GA13221@amd> References: <1497951359-13334-1-git-send-email-benjamin.gaignard@linaro.org> <20170620100348.zh4ygvjjgnhxvmvl@piout.net> Reply-To: rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" Cc: Benjamin Gaignard , linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org, adi-buildroot-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Alessandro Zummo , Gregory Clement , Ingo Molnar , Jason Cooper , John Stultz , linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Linus Walleij , Michael Chan , netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org, Sebastian Hesselbarth , Support Opensource , Thomas Gleixner , x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, Baruch Siach , Hans Ulli Kroll , Vladimir Zapolskiy , Sylvain Lemieux , Barry Song Return-path: Sender: rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Content-Disposition: inline In-Reply-To: <20170620100348.zh4ygvjjgnhxvmvl-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org> List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , List-Id: netdev.vger.kernel.org --UugvWAfsgieZRqgk Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline On Tue 2017-06-20 12:03:48, Alexandre Belloni wrote: > On 20/06/2017 at 11:35:08 +0200, Benjamin Gaignard wrote: > > rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they > > rely on 32bits variables and that will make rtc break in y2038/2016. > > Please don't, because this hide the fact that the hardware will not > handle dates in y2038 anyway and as pointed by Russell a few month ago, > rtc_time_to_tm will be able to catch it but the 64 bit version will > silently ignore it. Reference? Because rtc on PCs stores date in binary coded decimal, so it is likely to break in 2100, not 2038... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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. --- 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 email to rtc-linux+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit https://groups.google.com/d/optout. --UugvWAfsgieZRqgk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAllJEKMACgkQMOfwapXb+vLe9wCgu9cyUI440c/59xBQrQRexyjC q9UAnRKqRfLSYD/VIlYozWlk+CWfUWFP =o49/ -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: pavel@ucw.cz (Pavel Machek) Date: Tue, 20 Jun 2017 14:10:11 +0200 Subject: [PATCH 00/51] rtc: stop using rtc deprecated functions In-Reply-To: <20170620100348.zh4ygvjjgnhxvmvl@piout.net> References: <1497951359-13334-1-git-send-email-benjamin.gaignard@linaro.org> <20170620100348.zh4ygvjjgnhxvmvl@piout.net> Message-ID: <20170620121011.GA13221@amd> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tue 2017-06-20 12:03:48, Alexandre Belloni wrote: > On 20/06/2017 at 11:35:08 +0200, Benjamin Gaignard wrote: > > rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they > > rely on 32bits variables and that will make rtc break in y2038/2016. > > Please don't, because this hide the fact that the hardware will not > handle dates in y2038 anyway and as pointed by Russell a few month ago, > rtc_time_to_tm will be able to catch it but the 64 bit version will > silently ignore it. Reference? Because rtc on PCs stores date in binary coded decimal, so it is likely to break in 2100, not 2038... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: Digital signature URL: