From: Su Yue <suy.fnst@cn.fujitsu.com>
To: "Stéphane Lesimple" <stephane_btrfs@lesimple.fr>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2] btrfs-progs: fix nanosecs in task_period_start
Date: Thu, 5 Jul 2018 15:53:40 +0800 [thread overview]
Message-ID: <30c8d16c-6cc3-cfc7-8068-87d30954c988@cn.fujitsu.com> (raw)
In-Reply-To: <1530732014-5449-2-git-send-email-stephane_btrfs@lesimple.fr>
On 07/05/2018 03:20 AM, Stéphane Lesimple wrote:
> This is a single-line fix on the preexisting task_period_start function.
>
> Signed-off-by: Stéphane Lesimple <stephane_btrfs@lesimple.fr>
Reviewed-by: Su Yue <suy.fnst@cn.fujitsu.com>
> ---
> task-utils.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/task-utils.c b/task-utils.c
> index 12b0002..284cbb3 100644
> --- a/task-utils.c
> +++ b/task-utils.c
> @@ -102,7 +102,7 @@ int task_period_start(struct task_info *info, unsigned int period_ms)
> info->periodic.wakeups_missed = 0;
>
> sec = period_ms / 1000;
> - ns = (period_ms - (sec * 1000)) * 1000;
> + ns = (period_ms - (sec * 1000)) * 1000 * 1000;
> itval.it_interval.tv_sec = sec;
> itval.it_interval.tv_nsec = ns;
> itval.it_value.tv_sec = sec;
>
next prev parent reply other threads:[~2018-07-05 7:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 19:20 [PATCH 0/2] btrfs-progs: check: enhanced progress indicator Stéphane Lesimple
2018-07-04 19:20 ` [PATCH 1/2] btrfs-progs: fix nanosecs in task_period_start Stéphane Lesimple
2018-07-05 7:53 ` Su Yue [this message]
2018-07-04 19:20 ` [PATCH 2/2] btrfs-progs: check: enhanced progress indicator Stéphane Lesimple
2018-07-11 5:18 ` Qu Wenruo
2018-07-16 16:55 ` David Sterba
2018-07-17 1:23 ` Misono Tomohiro
2018-07-17 12:09 ` David Sterba
2018-07-16 16:48 ` [PATCH 0/2] " David Sterba
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=30c8d16c-6cc3-cfc7-8068-87d30954c988@cn.fujitsu.com \
--to=suy.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=stephane_btrfs@lesimple.fr \
/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).