This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC 7/7] y2038: Introduce support for clock_settime() being Y2038 safe
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Lukasz Majewski <lukma at denx dot de>
- Cc: <libc-alpha at sourceware dot org>, Paul Eggert <eggert at cs dot ucla dot edu>, Zack Weinberg <zackw at panix dot com>
- Date: Wed, 27 Mar 2019 13:48:13 +0000
- Subject: Re: [RFC 7/7] y2038: Introduce support for clock_settime() being Y2038 safe
- References: <20190327085210.22019-1-lukma@denx.de> <20190327085210.22019-8-lukma@denx.de>
On Wed, 27 Mar 2019, Lukasz Majewski wrote:
> +/* For Y2038 safe system the __clock_settime64 needs to be a visible
> + symbol as a replacement for Y2038 unsafe clock_settime()
> +*/
Do not use () after a function name to indicate it's a function; see the
GNU Coding Standards. This applies to other comments in this patch series
as well.
--
Joseph S. Myers
joseph@codesourcery.com