On Tue, 21 Mar 2017, Arnd Bergmann wrote:
> On Mon, Mar 20, 2017 at 9:40 PM, Thomas Gleixner wrote:
> > On Mon, 20 Mar 2017, Deepa Dinamani wrote:
> >> >> -static int ptp_clock_getres(struct posix_clock *pc, struct timespec
> >> >> *tp)
> >> >> +static int
On Mon, Mar 20, 2017 at 9:40 PM, Thomas Gleixner wrote:
> On Mon, 20 Mar 2017, Deepa Dinamani wrote:
>> >> -static int ptp_clock_getres(struct posix_clock *pc, struct timespec *tp)
>> >> +static int ptp_clock_getres(struct posix_clock *pc, struct timespec64
>> >> *tp)
>> >
>>
On Sun, 19 Mar 2017 11:51:34 +0100 (CET)
Thomas Gleixner wrote:
> On Sat, 18 Mar 2017, Deepa Dinamani wrote:
>
> > struct timespec is not y2038 safe.
> > Replace the posix_clock ops interfaces to use
> > struct timespec64.
> > The patch also changes struct itimerspec
> Please do not explain WHAT the patch is doing. We can see that from the
> diff itself. What's important is the WHY. A good changelog is structured in
> paragraphs, which explain the context, the problem and the solution. Please
> read Documentation/process/submitting-patches.rst. Let me give you
> When changing the PTP code, please put the PTP maintainer onto CC.
Will do. Thanks for pointing out the omission.
-Deepa
___
Y2038 mailing list
Y2038@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/y2038
On Sat, Mar 18, 2017 at 10:17:41PM -0700, Deepa Dinamani wrote:
> struct timespec is not y2038 safe.
> Replace the posix_clock ops interfaces to use
> struct timespec64.
> The patch also changes struct itimerspec interfaces to
> struct itimerspec64 as itimerspec internally uses timespec
>
On Sat, 18 Mar 2017, Deepa Dinamani wrote:
> struct timespec is not y2038 safe.
> Replace the posix_clock ops interfaces to use
> struct timespec64.
> The patch also changes struct itimerspec interfaces to
> struct itimerspec64 as itimerspec internally uses timespec
> and itimerspec64 uses