From: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
To: Arnd Bergmann <arnd@arndb.de>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: y2038@lists.linaro.org, Hannes Reinecke <hare@suse.de>,
Johannes Thumshirn <jthumshirn@suse.de>,
James Smart <jsmart2021@gmail.com>, Jens Axboe <axboe@kernel.dk>,
Steffen Maier <maier@linux.vnet.ibm.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi_transport_fc: use 64-bit timestamps consistently
Date: Mon, 25 Jun 2018 12:30:13 -0700 [thread overview]
Message-ID: <3161ed3e-1237-6e80-2f3a-79cb8179a417@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180618153004.1808419-1-arnd@arndb.de>
On 06/18/2018 08:29 AM, Arnd Bergmann wrote:
> The get_seconds() helper returns an 'unsigned long' value, which can
> overflow on 32-bit architectures. Since the interface we pass it into
> already uses a 64-bit type, we can just use ktime_get_real_seconds()
> instead.
>
> While we generally prefer local timestamps in CLOCK_MONOTONIC format
> (ktime_get_seconds), this keeps using the CLOCK_REALTIME version
> in order to maintain compatibility with existing code.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
Reviewed-by: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
next prev parent reply other threads:[~2018-06-25 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 15:29 [PATCH] scsi_transport_fc: use 64-bit timestamps consistently Arnd Bergmann
2018-06-25 7:50 ` Johannes Thumshirn
2018-06-25 19:30 ` Tyrel Datwyler [this message]
2018-06-25 19:56 ` James Smart
2018-06-26 15:59 ` Martin K. Petersen
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=3161ed3e-1237-6e80-2f3a-79cb8179a417@linux.vnet.ibm.com \
--to=tyreld@linux.vnet.ibm.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=jsmart2021@gmail.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=maier@linux.vnet.ibm.com \
--cc=martin.petersen@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).