From: Karel Zak <kzak@redhat.com>
To: J William Piggott <elseifthen@gmx.com>
Cc: Benno Schulenberg <bensberg@justemail.net>,
Util-Linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 4/5] hwclock: add '11 minute mode' information
Date: Wed, 18 Mar 2015 10:43:07 +0100 [thread overview]
Message-ID: <20150318094307.GZ28925@ws.net.home> (raw)
In-Reply-To: <5508D1E0.205@gmx.com>
On Tue, Mar 17, 2015 at 09:16:16PM -0400, J William Piggott wrote:
>
>
> On 03/17/2015 05:57 AM, Karel Zak wrote:
> > On Sun, Mar 15, 2015 at 04:47:27PM +0100, Benno Schulenberg wrote:
> >> "When in this state, bit 6 (the bit that is set in the mask 0x0040)
> >> of the kernel's time_status variable is *unset*."
> >
> > Yes, this is more readable (at least for me:-).
>
> I explained to Mr Schulenbuerg that I wrote it that way for layman users.
> Are they going to understand 'the bit that is set in the mask 0x0040'?
I have doubts it will be readable for layman users at all
independently on used words :-) Now it's at least readable for
advanced users. If you want to make it really readable for layman
users than add and example to the man page.
> What does that even mean? What does 'mask' have to do with it? It could
> simply say "the bit that is set by binary 0x0040"
> How does that differ from saying the binary 64's bit?
>
> Using hex will help the average user how?
>
> I used decimal because adjtimex displays the status variable as a decimal
> number:
>
> adjtimex -p
> status: 8193
>
> adjtimex -p
> status: 8257
>
> Which one is synchronized?
$ echo $((8193 & 0x0040))
0
$ echo $((8257 & 0x0040))
64
and frankly it's adjtimex mistake that it does not provide the
information in more human readable way.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2015-03-18 9:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 19:11 [PATCH 1/5] hwclock: add TZDIR J William Piggott
2015-03-13 19:15 ` [PATCH 2/5] hwclock: Improve FILES section J William Piggott
2015-03-13 19:18 ` [PATCH 3/5] hwclock: remove depreciated ntpdate J William Piggott
2015-03-15 15:26 ` Benno Schulenberg
2015-03-16 0:19 ` Isaac Dunham
2015-03-16 10:33 ` Karel Zak
2015-03-17 3:37 ` J William Piggott
2015-03-17 9:29 ` Karel Zak
2015-03-17 21:10 ` J William Piggott
2015-03-13 19:22 ` [PATCH 4/5] hwclock: add '11 minute mode' information J William Piggott
2015-03-15 15:47 ` Benno Schulenberg
2015-03-17 9:57 ` Karel Zak
2015-03-18 1:16 ` J William Piggott
2015-03-18 9:43 ` Karel Zak [this message]
2015-03-13 19:26 ` [PATCH 5/5] hwclock: man-page errata J William Piggott
2015-03-15 15:51 ` Benno Schulenberg
2015-03-15 15:20 ` [PATCH 1/5] hwclock: add TZDIR Benno Schulenberg
2015-03-16 10:30 ` Karel Zak
2015-03-17 9:58 ` 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=20150318094307.GZ28925@ws.net.home \
--to=kzak@redhat.com \
--cc=bensberg@justemail.net \
--cc=elseifthen@gmx.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