From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Vasu Dev <vasu.dev@intel.com>,
"y2038@lists.linaro.org" <y2038@lists.linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"fcoe-devel@open-fcoe.org" <fcoe-devel@open-fcoe.org>
Subject: Re: [PATCH] scsi: libfc: fix seconds_since_last_reset calculation
Date: Mon, 20 Jun 2016 16:58:11 +0200 [thread overview]
Message-ID: <7eea4ce5-8cc4-d982-57ac-ec6e8d8ba323@sandisk.com> (raw)
In-Reply-To: <3671744.A3ustGCdmM@wuerfel>
On 06/20/2016 04:48 PM, Arnd Bergmann wrote:
> On Monday, June 20, 2016 3:54:06 PM CEST Bart Van Assche wrote:
>> On 06/17/2016 05:47 PM, Arnd Bergmann wrote:
>>> - jiffies_to_timespec(jiffies, &v0);
>>> - jiffies_to_timespec(lport->boot_time, &v1);
>>> - fc_stats->seconds_since_last_reset = (v0.tv_sec - v1.tv_sec);
>>> + fc_stats->seconds_since_last_reset = (lport->boot_time - jiffies) / HZ;
>>
>> Does this patch introduce a 64-bit division? There might still be 32-bit
>> users of this code.
>
> No, both lport->boot_time and jiffies are 'unsigned long'.
Ah, you're right. Hence:
Reviewed-by: Bart Van Assche <bart.vanassche@sandisk.com>
_______________________________________________
Y2038 mailing list
Y2038@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/y2038
next prev parent reply other threads:[~2016-06-20 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 15:47 [PATCH] scsi: libfc: fix seconds_since_last_reset calculation Arnd Bergmann
2016-06-20 13:54 ` Bart Van Assche
2016-06-20 14:50 ` Arnd Bergmann
2016-06-20 14:58 ` Bart Van Assche [this message]
2016-06-21 2:05 ` 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=7eea4ce5-8cc4-d982-57ac-ec6e8d8ba323@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=arnd@arndb.de \
--cc=fcoe-devel@open-fcoe.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=vasu.dev@intel.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