From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Eric Rannaud <eric.rannaud@gmail.com>
Cc: Eric Rannaud <e@nanocritical.com>,
linux-man <linux-man@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: [PATCH 1/1] clock_getres.2: dynamic POSIX clock devices can return other errors
Date: Thu, 2 Apr 2020 22:19:45 +0200 [thread overview]
Message-ID: <CAKgNAkipcX47quv23SACeorSexO00nUAJR3QSTA3bFNMresE4Q@mail.gmail.com> (raw)
In-Reply-To: <CA+zRj8XYLpa_gep+VxUfQuqeKu+=thMit-jNv1soC8Mh5H43Ug@mail.gmail.com>
Hello Éric,
On Thu, 2 Apr 2020 at 22:07, Eric Rannaud <eric.rannaud@gmail.com> wrote:
>
> Micheal,
>
> I'm conscious that saying "dynamic POSIX clock device" without any
> explanation may be too obscure for a man page.
It's true that more detail would be nice, but...
> There is documentation in:
> - include/linux/posix-clock.h
> - Documentation/driver-api/ptp.rst (explicitly states that EOPNOTSUPP
> should be returned)
(Is this a reference to the tack that I tweaked your patch to change
EOPNOTSUPP to ENOTSUP?)
> - include/uapi/linux/ptp_clock.h
... it's a bit of a stretch to call any of those documentation, since
they don't really describe the concept of a dynamic POSIX clock
device.
>
> (IEEE 1588 PTP is the canonical user of these dynamic clock devices)
>
> Would you want to refer to any of these from the man page?
See above. I would be happy to add a 2 or 3 sentence note to the page
that briefly describes the concept of a POSIX clock. Would you be able
to come up with something?
> Thanks for maintaining this project!
Thanks. Though it has suffered a lot of neglect of late :-(.
Cheers,
Michael
next prev parent reply other threads:[~2020-04-02 20:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 18:02 clock_settime(2) error for non-settable clocks Eric Rannaud
2020-03-21 3:56 ` Aleksa Sarai
2020-03-26 8:37 ` Michael Kerrisk (man-pages)
2020-03-29 20:49 ` Michael Kerrisk (man-pages)
2020-04-02 11:48 ` Michael Kerrisk (man-pages)
2020-04-02 14:23 ` [PATCH 1/1] clock_getres.2: dynamic POSIX clock devices can return other errors Eric Rannaud
2020-04-02 19:55 ` Michael Kerrisk (man-pages)
2020-04-02 20:06 ` Eric Rannaud
2020-04-02 20:19 ` Michael Kerrisk (man-pages) [this message]
2020-04-02 20:49 ` Eric Rannaud
2020-04-02 20:50 ` Eric Rannaud
2020-04-03 7:02 ` Michael Kerrisk (man-pages)
2020-04-03 16:42 ` Eric Rannaud
2020-04-20 11:13 ` Michael Kerrisk (man-pages)
2020-04-02 14:29 ` clock_settime(2) error for non-settable clocks Eric Rannaud
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=CAKgNAkipcX47quv23SACeorSexO00nUAJR3QSTA3bFNMresE4Q@mail.gmail.com \
--to=mtk.manpages@gmail.com \
--cc=e@nanocritical.com \
--cc=eric.rannaud@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-man@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;
as well as URLs for NNTP newsgroup(s).