From: Karel Zak <kzak@redhat.com>
To: kerolasa@gmail.com
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: [git pull] hwclock fixes
Date: Tue, 26 Jul 2011 16:22:12 +0200 [thread overview]
Message-ID: <20110726142212.GB14764@nb.net.home> (raw)
In-Reply-To: <CAG27Bk0EkOe=dbt88PFtDKwyo9+0mZPaysVh0eM9BjWu4X8+vQ@mail.gmail.com>
On Tue, Jul 26, 2011 at 12:42:46AM +0200, Sami Kerola wrote:
> are available in the git repository at:
> https://github.com/kerolasa/lelux-utiliteetit hwclock
>
> hwclock: remove clock-ppc.c
OK
> hwclock: remove misleading information
OK
> hwclock: coding style clean up
OK
> hwclock: include-what-you-use header check
Hmm.. I see something completely different in the patch:
Showing 5 changed files with 171 additions and 216 deletions.
it seems like "use libc error facilities".
> hwclock: move path definitions to pathnames.h
OK
> hwclock: remove inb & outb functions
Are you really sure? I think it depends on the header files, for
example it seems GNU Hurd reads information from cmos
http://www.spinics.net/lists/util-linux-ng/msg04179.html
and we already talked about it:
http://www.spinics.net/lists/util-linux-ng/index.html#04673
> hwclock: fix compiler warnings
This is wrong for __alpha__ code where the variables are used.
Move the comment before the function and the begin of the function to
the #ifndef __alpha_ block, then you can use __unused__ for non-aplha
only.
> hwclock: remove goto statement
OK
> hwclock: add variable initialization
Good catch.
> hwclock: move long options away from global scope
But the enum {} does not have to be in the main().
> hwclock: validate numeric option arguments
OK
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2011-07-26 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 22:42 [git pull] hwclock fixes Sami Kerola
2011-07-26 14:22 ` Karel Zak [this message]
2011-07-26 16:38 ` Sami Kerola
2011-07-27 9:16 ` Karel Zak
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=20110726142212.GB14764@nb.net.home \
--to=kzak@redhat.com \
--cc=kerolasa@gmail.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