From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: pang.xunlei@linaro.org, peterz@infradead.org, fweisbec@gmail.com,
heiko.carstens@de.ibm.com, paulus@samba.org, cl@linux.com,
heenasirwani@gmail.com, linux-arch@vger.kernel.org,
linux-s390@vger.kernel.org, y2038@lists.linaro.org,
rafael.j.wysocki@intel.com, ahh@google.com, pjt@google.com,
riel@redhat.com, richardcochran@gmail.com, tj@kernel.org,
john.stultz@linaro.org, tglx@linutronix.de, rth@twiddle.net,
Baolin Wang <baolin.wang@linaro.org>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, schwidefsky@de.ibm.com,
linux390@de.ibm.com
Subject: Re: [PATCH v3 00/22] Convert the posix_clock_operations and k_clock structure to ready for 2038
Date: Tue, 12 May 2015 11:39:36 +0200 [thread overview]
Message-ID: <2293496.0Ycckx2zYU@wuerfel> (raw)
In-Reply-To: <1431342518-29362-1-git-send-email-baolin.wang@linaro.org>
On Monday 11 May 2015 19:08:38 Baolin Wang wrote:
> This patch series changes the 32-bit time type (timespec/itimerspec) to the 64-bit one
> (timespec64/itimerspec64), since 32-bit time types will break in the year 2038.
>
> This patch series introduces new methods with timespec64/itimerspec64 type,
> and removes the old ones with timespec/itimerspec type for posix_clock_operations
> and k_clock structure.
>
> Also introduces some new functions with timespec64/itimerspec64 type, like current_kernel_time64(),
> hrtimer_get_res64(), cputime_to_timespec64() and timespec64_to_cputime().
>
> Changes since v2:
> -Split the syscall conversion patch into small some patches.
>
>
> Baolin Wang (22):
> linux/time64.h:Introduce the 'struct itimerspec64' for 64bit
> timekeeping:Introduce the current_kernel_time64() function with
> timespec64 type
> time/hrtimer:Introduce hrtimer_get_res64() with timespec64 type for
> getting the timer resolution
> posix-timers:Split out the guts of the syscall and change the
> implementation for timer_gettime
> posix-timers:Convert to the 64bit methods for the timer_gettime
> syscall function
I have two more very general comments about the series:
a) something has gone wrong with your submission in v2 and v3 but was
working earlier: normally all emails should be sent by git-send-email
as replies to the [patch 00/22] mail. This is the default, and it
is enabled by the '--thread --no-chain-reply' options. Please try
to get this to work again.
b) it would be better to have a little shorter subject lines, to avoid
line-wrapping in the list above. Here are some examples what you could
use to replace the lines above:
timekeeping: introduce struct itimerspec64
timekeeping: introduce current_kernel_time64()
hrtimer: introduce hrtimer_get_res64()
posix-timers: split up sys_timer_gettime()
posix-timers: convert timer_gettime() to timespec64
In general, try to come up with the shortest description that
uniquely describes what your patch does, and move any details into
the longer patch description.
Arnd
_______________________________________________
Y2038 mailing list
Y2038@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/y2038
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: Baolin Wang <baolin.wang@linaro.org>,
tglx@linutronix.de, pang.xunlei@linaro.org, peterz@infradead.org,
heiko.carstens@de.ibm.com, paulus@samba.org, cl@linux.com,
heenasirwani@gmail.com, linux-arch@vger.kernel.org,
linux-s390@vger.kernel.org, y2038@lists.linaro.org,
rafael.j.wysocki@intel.com, ahh@google.com, fweisbec@gmail.com,
pjt@google.com, riel@redhat.com, richardcochran@gmail.com,
schwidefsky@de.ibm.com, john.stultz@linaro.org, rth@twiddle.net,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, tj@kernel.org, linux390@de.ibm.com
Subject: Re: [PATCH v3 00/22] Convert the posix_clock_operations and k_clock structure to ready for 2038
Date: Tue, 12 May 2015 11:39:36 +0200 [thread overview]
Message-ID: <2293496.0Ycckx2zYU@wuerfel> (raw)
Message-ID: <20150512093936.xiyAj21VyVIyB7xFcP9nfwEHc7ACOPHSHmfOX2fMpek@z> (raw)
In-Reply-To: <1431342518-29362-1-git-send-email-baolin.wang@linaro.org>
On Monday 11 May 2015 19:08:38 Baolin Wang wrote:
> This patch series changes the 32-bit time type (timespec/itimerspec) to the 64-bit one
> (timespec64/itimerspec64), since 32-bit time types will break in the year 2038.
>
> This patch series introduces new methods with timespec64/itimerspec64 type,
> and removes the old ones with timespec/itimerspec type for posix_clock_operations
> and k_clock structure.
>
> Also introduces some new functions with timespec64/itimerspec64 type, like current_kernel_time64(),
> hrtimer_get_res64(), cputime_to_timespec64() and timespec64_to_cputime().
>
> Changes since v2:
> -Split the syscall conversion patch into small some patches.
>
>
> Baolin Wang (22):
> linux/time64.h:Introduce the 'struct itimerspec64' for 64bit
> timekeeping:Introduce the current_kernel_time64() function with
> timespec64 type
> time/hrtimer:Introduce hrtimer_get_res64() with timespec64 type for
> getting the timer resolution
> posix-timers:Split out the guts of the syscall and change the
> implementation for timer_gettime
> posix-timers:Convert to the 64bit methods for the timer_gettime
> syscall function
I have two more very general comments about the series:
a) something has gone wrong with your submission in v2 and v3 but was
working earlier: normally all emails should be sent by git-send-email
as replies to the [patch 00/22] mail. This is the default, and it
is enabled by the '--thread --no-chain-reply' options. Please try
to get this to work again.
b) it would be better to have a little shorter subject lines, to avoid
line-wrapping in the list above. Here are some examples what you could
use to replace the lines above:
timekeeping: introduce struct itimerspec64
timekeeping: introduce current_kernel_time64()
hrtimer: introduce hrtimer_get_res64()
posix-timers: split up sys_timer_gettime()
posix-timers: convert timer_gettime() to timespec64
In general, try to come up with the shortest description that
uniquely describes what your patch does, and move any details into
the longer patch description.
Arnd
next prev parent reply other threads:[~2015-05-12 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 11:08 [PATCH v3 00/22] Convert the posix_clock_operations and k_clock structure to ready for 2038 Baolin Wang
2015-05-12 9:39 ` Arnd Bergmann [this message]
2015-05-12 9:39 ` Arnd Bergmann
2015-05-12 14:16 ` Baolin Wang
-- strict thread matches above, loose matches on Subject: below --
2015-05-11 11:06 Baolin Wang
2015-05-11 11:06 ` Baolin Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2293496.0Ycckx2zYU@wuerfel \
--to=arnd@arndb.de \
--cc=ahh@google.com \
--cc=baolin.wang@linaro.org \
--cc=cl@linux.com \
--cc=fweisbec@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heenasirwani@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=john.stultz@linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=pang.xunlei@linaro.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rafael.j.wysocki@intel.com \
--cc=richardcochran@gmail.com \
--cc=riel@redhat.com \
--cc=rth@twiddle.net \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=y2038@lists.linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox