From: lijiang <lijiang@redhat.com>
To: Petr Tesarik <ptesarik@suse.cz>
Cc: Masaki Tachibana <mas-tachibana@vf.jp.nec.com>,
Daisuke Nishimura <dai-nishimura@rc.jp.nec.com>,
Dave Young <dyoung@redhat.com>,
Takuya Nakayama <tak-nakayama@tg.jp.nec.com>,
kexec-ml <kexec@lists.infradead.org>
Subject: Re: [PATCH] makedumpfile: Do not print ETA value if current progress is 0
Date: Wed, 20 Jun 2018 19:24:59 +0800 [thread overview]
Message-ID: <7d1bf253-89af-a6f9-4579-04378e514d71@redhat.com> (raw)
In-Reply-To: <20180620091733.290580b9@ezekiel.suse.cz>
在 2018年06月20日 15:17, Petr Tesarik 写道:
> Hi Lianbo,
>
> On Wed, 20 Jun 2018 11:07:46 +0800
> lijiang <lijiang@redhat.com> wrote:
>
>> 在 2018年04月10日 15:47, Petr Tesarik 写道:
>> [...]
>>> Yes, the current code will not produce sensible results if the system
>>> clock moves backwards. With my patch it will most likely say: ">2day".
>>> But it will not work any better if you use a 64-bit integer.
>>>
>>> Instead, we should be using clock_gettime(CLOCK_MONOTONIC, ...).
>>> That's a separate issue that I can solve in another patch.
>> Hi, Petr
>> Previously mentioned that you would solve this issue, would you have any plans
>> about this issue?
>
> Thank you for the reminder. Yes, let me do it now!
>
> Petr T
>
Swift action! I have seen your patches, thank you.
Lianbo
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2018-06-20 11:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 9:40 [PATCH] makedumpfile: Do not print ETA value if current progress is 0 Petr Tesarik
2018-04-10 7:09 ` lijiang
2018-04-10 7:47 ` Petr Tesarik
2018-04-10 8:28 ` Petr Tesarik
2018-04-10 11:39 ` [PATCH v2] makedumpfile: Use integer arithmetics for the progress bar Petr Tesarik
2018-05-18 8:22 ` Masaki Tachibana
2018-05-18 12:46 ` Petr Tesarik
2018-06-20 3:07 ` [PATCH] makedumpfile: Do not print ETA value if current progress is 0 lijiang
2018-06-20 7:17 ` Petr Tesarik
2018-06-20 11:24 ` lijiang [this message]
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=7d1bf253-89af-a6f9-4579-04378e514d71@redhat.com \
--to=lijiang@redhat.com \
--cc=dai-nishimura@rc.jp.nec.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=mas-tachibana@vf.jp.nec.com \
--cc=ptesarik@suse.cz \
--cc=tak-nakayama@tg.jp.nec.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.