From: Karel Zak <kzak@redhat.com>
To: Chris MacGregor <chrismacgregor@google.com>
Cc: util-linux@vger.kernel.org, Chris MacGregor <chris@cybermato.com>
Subject: Re: [PATCH] hwclock: fix possible hang and other set_hardware_clock_exact() issues
Date: Wed, 5 Mar 2014 12:52:29 +0100 [thread overview]
Message-ID: <20140305115229.GF13353@x2.net.home> (raw)
In-Reply-To: <vcw5ha7kiekk.fsf@chrismacgregor0.sea.corp.google.com>
On Thu, Feb 27, 2014 at 10:40:59AM -0800, Chris MacGregor wrote:
> diff --git a/sys-utils/hwclock.c b/sys-utils/hwclock.c
> index 30660d4..161d5cf 100644
> --- a/sys-utils/hwclock.c
> +++ b/sys-utils/hwclock.c
Looks good, it's really more robust solution (and with nice debug
output:-)
Applied, thanks!
I did two cosmetic changes to the code (define variables at the begin
of the code block rather than later in code).
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2014-03-05 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 18:40 [PATCH] hwclock: fix possible hang and other set_hardware_clock_exact() issues Chris MacGregor
2014-03-05 11:52 ` Karel Zak [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=20140305115229.GF13353@x2.net.home \
--to=kzak@redhat.com \
--cc=chris@cybermato.com \
--cc=chrismacgregor@google.com \
--cc=util-linux@vger.kernel.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