[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK8P3a3hXBZqubqehcTzn037aa-KVAeg82gY630oN3Btnkvdcw@mail.gmail.com>
Date: Thu, 15 Mar 2018 16:46:32 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: lkml <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
John Stultz <john.stultz@...aro.org>,
Miroslav Lichvar <mlichvar@...hat.com>,
Richard Cochran <richardcochran@...il.com>,
Prarit Bhargava <prarit@...hat.com>,
Stephen Boyd <sboyd@...nel.org>,
Deepa Dinamani <deepa.kernel@...il.com>
Subject: Re: [PATCH] [v2] y2038: introduce struct __kernel_old_timeval
On Thu, Mar 15, 2018 at 9:44 AM, Thomas Gleixner <tglx@...utronix.de> wrote:
> On Wed, 14 Mar 2018, Arnd Bergmann wrote:
>>
>> /*
>> + * legacy timeval structure, only embedded in structures that
>> + * traditionally used 'timeval' to pass time intervals (not absolute
>> + * times). Do not add new users. If user space fails to compile
>> + * here, this is probably because it is not y2038 safe and needs to
>> + * be changed to use another interface.
>> + */
>> +struct __kernel_old_timeval {
>> + __kernel_long_t tv_sec; /* seconds */
>> + __kernel_long_t tv_usec; /* microseconds */
>
> Please don't use these horrible tail comments. If you want to document the
> obvious, then please use proper kernel doc.
I just removed them now, the only reason they were there is to keep
the style in sync with the rest of the file, but it's also just a lot of
duplication.
Arnd
Powered by blists - more mailing lists