timespec is deprecated because of the y2038 overflow, so let's convert
this one to ktime_get_ts64(). The code is already safe even on 32-bit
architectures, since it uses monotonic times. On 64-bit architectures,
nothing changes, while on 32-bit architectures this avoids one
type conversion.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
net/openvswitch/flow.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
On Mon, Nov 27, 2017 at 5:11 PM, Arnd Bergmann [off-list ref] wrote:
quoted hunk
timespec is deprecated because of the y2038 overflow, so let's convert
this one to ktime_get_ts64(). The code is already safe even on 32-bit
architectures, since it uses monotonic times. On 64-bit architectures,
nothing changes, while on 32-bit architectures this avoids one
type conversion.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
net/openvswitch/flow.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
On Tue, Nov 28, 2017 at 5:59 AM, Pravin Shelar [off-list ref] wrote:
On Mon, Nov 27, 2017 at 5:11 PM, Arnd Bergmann [off-list ref] wrote:
quoted
timespec is deprecated because of the y2038 overflow, so let's convert
this one to ktime_get_ts64(). The code is already safe even on 32-bit
architectures, since it uses monotonic times. On 64-bit architectures,
nothing changes, while on 32-bit architectures this avoids one
type conversion.
Signed-off-by: Arnd Bergmann <redacted>
---
net/openvswitch/flow.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
It was a micro-optimization that I did to turn a 's64 * constant -> s64'
operation into a cheaper 's32 * constant -> s64' operation. If you
prefer, I can sent it again with a comment, or drop the two
casts.
Arnd
timespec is deprecated because of the y2038 overflow, so let's convert
this one to ktime_get_ts64(). The code is already safe even on 32-bit
architectures, since it uses monotonic times. On 64-bit architectures,
nothing changes, while on 32-bit architectures this avoids one
type conversion.
Signed-off-by: Arnd Bergmann <redacted>