diff options
| author | Alejandro Colomar <alx@kernel.org> | 2022-12-04 20:38:06 +0100 |
|---|---|---|
| committer | Alejandro Colomar <alx@kernel.org> | 2022-12-04 20:39:41 +0100 |
| commit | b324e17d3208c940622ab192609b836928d5aa8d (patch) | |
| tree | de6403ed6aaad3b403607aeb1624f2b193e50590 /man2/getitimer.2 | |
| parent | 0137c7f49c178c14c230a0b89e2979732a52e6df (diff) | |
| download | man-pages-b324e17d3208c940622ab192609b836928d5aa8d.tar.gz | |
Many pages: wfix
Refer consistently to software versions. In most cases, it is done as
<software> <version>. In the case of Linux and glibc, use the project
name, instead of other terms such as 'kernel' or 'library'.
I found the uses of inconsistent language with the following:
$ find man* -type f \
| xargs grep -i '\(since\|before\|after\|until\|to\|from\|in\|between\|version\|with\) \(kernel\|version\|2\.\|3\.\|4\.\|5\.\)' \
| sort
However, I might have missed some cases. Anyway, 99% consistency is
pretty good consistency. We'll fix the remaining cases as we see them.
Signed-off-by: Alejandro Colomar <alx@kernel.org>
Diffstat (limited to 'man2/getitimer.2')
| -rw-r--r-- | man2/getitimer.2 | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/man2/getitimer.2 b/man2/getitimer.2 index 3c86acfd52..093752b620 100644 --- a/man2/getitimer.2 +++ b/man2/getitimer.2 @@ -227,7 +227,7 @@ timer may expire before the signal from a previous expiration has been delivered. The second signal in such an event will be lost. .PP -On Linux kernels before 2.6.16, timer values are represented in jiffies. +Before Linux 2.6.16, timer values are represented in jiffies. If a request is made set a timer with a value whose jiffies representation exceeds .B MAX_SEC_IN_JIFFIES @@ -243,10 +243,10 @@ the kernel uses a different internal representation for times, and this ceiling is removed. .PP On certain systems (including i386), -Linux kernels before version 2.6.12 have a bug which will produce +Linux kernels before Linux 2.6.12 have a bug which will produce premature timer expirations of up to one jiffy under some circumstances. -This bug is fixed in kernel 2.6.12. -.\" 4 Jul 2005: It looks like this bug may remain in 2.4.x. +This bug is fixed in Linux 2.6.12. +.\" 4 Jul 2005: It looks like this bug may remain in Linux 2.4.x. .\" http://lkml.org/lkml/2005/7/1/165 .PP POSIX.1-2001 says that @@ -254,10 +254,10 @@ POSIX.1-2001 says that should fail if a .I tv_usec value is specified that is outside of the range 0 to 999999. -However, in kernels up to and including 2.6.21, +However, up to and including Linux 2.6.21, Linux does not give an error, but instead silently adjusts the corresponding seconds value for the timer. -From kernel 2.6.22 onward, +From Linux 2.6.22 onward, this nonconformance has been repaired: an improper .I tv_usec |