On Mon, Dec 06, 2021 at 08:18:26PM +0100, Alejandro Colomar (man-pages) wrote:
> I think I slighly prefer "in a timespec(3) structure".
> However, I only slightly prefer that and don't really care that much, and
> will leave the final decision up to you.
It turned out very easy to rearrange all the pages to use this,
so they're all "timespec(3) structure" or "timespec(3) structures".
I've taken an additional liberty in stripping off
"as specified in <time.h>" from clock_getres.2: _nanosleep doesn't say
it, and they both live in <time.h> anyway.
наб (4):
clock_getres.2, clock_nanosleep.2, io_getevents.2, nanosleep.2,
poll.2, sched_rr_get_interval.2, select.2, sigwaitinfo.2,
timerfd_create.2, timer_settime.2, utimensat.2, mq_receive.3,
mq_send.3, pthread_tryjoin_np.3, sem_wait.3: replace in-line struct
timespec declarations with "timespec(3) structure" references
system_data_types.7: standardise on struct timespec fields comments to
ucase w/tv_nsec range
system_data_types.7: correct struct timespec::tv_nsec type for x32
system_data_types.7: note that struct timespec::tv_nsec being long
long on x32 is an extension
man2/clock_getres.2 | 15 +++------------
man2/clock_nanosleep.2 | 14 +++-----------
man2/io_getevents.2 | 14 ++++----------
man2/nanosleep.2 | 16 ++++------------
man2/poll.2 | 14 ++++----------
man2/sched_rr_get_interval.2 | 16 ++--------------
man2/select.2 | 14 ++++----------
man2/sigwaitinfo.2 | 14 ++++----------
man2/timer_settime.2 | 8 ++------
man2/timerfd_create.2 | 11 ++++-------
man2/utimensat.2 | 14 ++++----------
man3/mq_receive.3 | 14 ++++----------
man3/mq_send.3 | 14 ++++----------
man3/pthread_tryjoin_np.3 | 16 +++++-----------
man3/sem_wait.3 | 15 ++++-----------
man7/system_data_types.7 | 9 ++++++++-
16 files changed, 63 insertions(+), 155 deletions(-)
--
2.30.2
Attachment:
signature.asc
Description: PGP signature
