[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1504202154430.13914@nanos>
Date: Mon, 20 Apr 2015 21:59:01 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Baolin Wang <baolin.wang@...aro.org>
cc: arnd@...db.de, john.stultz@...aro.org, heenasirwani@...il.com,
pang.xunlei@...aro.org, peterz@...radead.org,
rafael.j.wysocki@...el.com, gregkh@...uxfoundation.org,
richardcochran@...il.com, benh@...nel.crashing.org,
paulus@...ba.org, mpe@...erman.id.au, schwidefsky@...ibm.com,
heiko.carstens@...ibm.com, linux390@...ibm.com, rth@...ddle.net,
riel@...hat.com, cl@...ux.com, tj@...nel.org, fweisbec@...il.com,
ahh@...gle.com, pjt@...gle.com, linuxppc-dev@...ts.ozlabs.org,
linux-s390@...r.kernel.org, linux-arch@...r.kernel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
y2038@...ts.linaro.org
Subject: Re: [PATCH 01/11] linux/time64.h:Introduce the 'struct itimerspec64'
for 64bit
On Mon, 20 Apr 2015, Thomas Gleixner wrote:
> On Mon, 20 Apr 2015, Baolin Wang wrote:
> > This patch introduces the 'struct itimerspec64' for 64bit to replace itimerspec,
> > and also introduces the conversion methods: itimerspec64_to_itimerspec() and
> > itimerspec_to_itimerspec64(), that makes itimerspec to ready for 2038 year.
> >
> > Signed-off-by: Baolin Wang <baolin.wang@...aro.org>
> > ---
> > include/linux/time64.h | 13 +++++++++++++
> > 1 file changed, 13 insertions(+)
> >
> > diff --git a/include/linux/time64.h b/include/linux/time64.h
> > index a383147..3647bdd 100644
> > --- a/include/linux/time64.h
> > +++ b/include/linux/time64.h
> > @@ -18,6 +18,11 @@ struct timespec64 {
> > };
> > #endif
> >
> > +struct itimerspec64 {
> > + struct timespec64 it_interval; /* timer period */
> > + struct timespec64 it_value; /* timer expiration */
> > +};
Aside of the macro mess. This really wants to be conditional on 64/32
but in the same way as we have the different implementations for
timespec64.
Your patch enforces a useless conversion from and to itimerspec64 even
on 64 bit because the compiler cannot map the types.
Sigh. timespec64 is a proper guidance here.
Thanks,
tglx
--
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