punctuate long numeric strings with digit separators
v2 cover punctuate long numeric strings with digit separators
man2/: use C digit separators with \\[aq] to show "'" or ISO/IEC suffixes to clarify long binary, octal, hex, decimal numeric strings; use consistent interval notation for value ranges;
fix minor discrepancies.
[PATCH 01/11] man2/shmget.2: fix limit units suffix from SI to IEC
[PATCH 02/11] man2/spu_run.2: fix example comment status code or-ed value
[PATCH 03/11] man2/: use consistent interval notation for value ranges
[PATCH 04/11] man2/open.2: punctuate octal perms with digit separators
[PATCH 05/11] man2/reboot.2: show BCD dates in hex not decimal
[PATCH 06/11] man2/reboot.2: punctuate hex in docs with digit separators
[PATCH 07/11] man2/statfs.2: punctuate hex in docs with digit separators
[PATCH 08/11] man2/adjtimex.2: use ISO/IEC suffixes and digit separators in ranges and example docs [PATCH 09/11] man2/getrandom.2: change limit to use IEC suffix
[PATCH 10/11] man2/futex.2: change limit to use ISO suffix
[PATCH 11/11] man2/: punctuate long numeric strings with digit separators
Brian Inglis (11):
man2/shmget.2: fix limit units suffix from SI to IEC
man2/spu_run.2: fix example comment status code or-ed value
man2/: use consistent interval notation for value ranges
man2/open.2: punctuate octal perms with digit separators
man2/reboot.2: show BCD dates in hex not decimal
man2/reboot.2: punctuate hex in docs with digit separators man2/statfs.2: punctuate hex in docs with digit separators man2/adjtimex.2: use ISO/IEC suffixes and digit separators in ranges and example docs man2/getrandom.2: change limit to use IEC suffix
man2/futex.2: change limit to use ISO suffix
man2/: punctuate long numeric strings with digit separators
man2/add_key.2 | 2 +- man2/adjtimex.2 | 12 ++--- man2/clock_getres.2 | 2 +- man2/clock_nanosleep.2 | 2 +- man2/eventfd.2 | 6 +-- man2/execve.2 | 2 +- man2/fcntl.2 | 4 +- man2/futex.2 | 2 +- man2/getitimer.2 | 4 +- man2/getrandom.2 | 2 +- man2/gettimeofday.2 | 2 +- man2/ioctl.2 | 4 +- man2/ioctl_console.2 | 2 +- man2/ioctl_getfsmap.2 | 4 +- man2/ioperm.2 | 2 +- man2/kexec_load.2 | 2 +- man2/link.2 | 4 +- man2/msgget.2 | 2 +- man2/nanosleep.2 | 4 +- man2/open.2 | 32 ++++++------ man2/pciconfig_read.2 | 2 +- man2/perf_event_open.2 | 2 +- man2/personality.2 | 8 +-- man2/prctl.2 | 2 +- man2/read.2 | 2 +- man2/reboot.2 | 24 ++++----- man2/semget.2 | 4 +- man2/sendfile.2 | 2 +- man2/shmget.2 | 2 +- man2/sigaction.2 | 4 +- man2/spu_run.2 | 8 +-- man2/statfs.2 | 110 ++++++++++++++++++++--------------------- man2/statx.2 | 2 +- man2/syscall.2 | 2 +- man2/timer_settime.2 | 4 +- man2/timerfd_create.2 | 2 +- man2/truncate.2 | 4 +- man2/utimensat.2 | 6 +-- man2/write.2 | 2 +- 39 files changed, 144 insertions(+), 144 deletions(-)
Signature · 1 line
2.39.0
PATCH v2 1/11 man2/shmget.2: fix limit units prefix symbol from SI to IEC
--- man2/shmget.2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
man2/shmget.2 +1 -1
@@ -354,7 +354,7 @@ for a discussion of why this default value (rather than is used. .IP From Linux 2.2 up to Linux 3.15, the default value of -this limit was 0x2000000 (32\ MB). +this limit was 0x2000000 (32\ MiB). .IP Because it is not possible to map just part of a shared memory segment, the amount of virtual memory places another limit on the maximum size of a
Re: [PATCH v2 01/11] man2/shmget.2: fix limit units prefix symbol from SI to IEC
On 2/8/23 21:27, Brian Inglis wrote:
Patch applied.
Thanks,
Alex
Quoted 4 lines
--- man2/shmget.2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Signature · 2 lines
<http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
PATCH v2 2/11 man2/spu_run.2: fix example comment status code or-ed value
In reply to Brian Inglis--- man2/spu_run.2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
man2/spu_run.2 +1 -1
@@ -245,7 +245,7 @@ int main(void) err(EXIT_FAILURE, "open"); /* - * We should see a status code of 0x1234002: + * We should see a status code of 0x12340002: * 0x00000002 (spu was stopped due to stop\-and\-signal) * | 0x12340000 (the stop\-and\-signal code) */
Alejandro Colomar
AppliedRe: [PATCH v2 02/11] man2/spu_run.2: fix example comment status code or-ed value
On 2/8/23 21:27, Brian Inglis wrote:
Applied.
Quoted 4 lines
--- man2/spu_run.2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Signature · 2 lines
<http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
PATCH v2 3/11 man2/: use consistent closed interval notation for value ranges
In reply to Brian Inglis--- man2/clock_getres.2 | 2 +- man2/clock_nanosleep.2 | 2 +- man2/getitimer.2 | 4 ++-- man2/gettimeofday.2 | 2 +- man2/nanosleep.2 | 4 ++-- man2/utimensat.2 | 2 +- 6 files changed, 8 insertions(+), 8 deletions(-)
man2/clock_getres.2 +1 -1
@@ -272,7 +272,7 @@ does not refer to a valid instance of a clock object. .I tp.tv_sec is negative or .I tp.tv_nsec -is outside the range [0..999,999,999]. +is outside the range [0, 999,999,999]. .TP .B EINVAL The
man2/clock_nanosleep.2 +1 -1
@@ -158,7 +158,7 @@ The sleep was interrupted by a signal handler; see .B EINVAL The value in the .I tv_nsec -field was not in the range 0 to 999999999 or +field was not in the range [0, 999999999] or .I tv_sec was negative. .TP
man2/getitimer.2 +2 -2
@@ -158,7 +158,7 @@ or (since Linux 2.6.22) one of the .I tv_usec fields in the structure pointed to by .I new_value -contains a value outside the range 0 to 999999. +contains a value outside the range [0, 999999]. .SH STANDARDS POSIX.1-2001, SVr4, 4.4BSD (this call first appeared in 4.2BSD). POSIX.1-2008 marks
@@ -253,7 +253,7 @@ POSIX.1-2001 says that .BR setitimer () should fail if a .I tv_usec -value is specified that is outside of the range 0 to 999999. +value is specified that is outside of the range [0, 999999]. 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.
man2/gettimeofday.2 +1 -1
@@ -152,7 +152,7 @@ is invalid. .I tv.tv_sec is negative or .I tv.tv_usec -is outside the range [0..999,999]. +is outside the range [0, 999999]. .TP .BR EINVAL " (since Linux 4.3)" .\" commit e1d7ba8735551ed79c7a0463a042353574b96da3
man2/nanosleep.2 +2 -2
@@ -66,7 +66,7 @@ The structure is used to specify intervals of time with nanosecond precision. .PP -The value of the nanoseconds field must be in the range 0 to 999999999. +The value of the nanoseconds field must be in the range [0, 999999999]. .PP Compared to .BR sleep (3)
@@ -106,7 +106,7 @@ again and continue with the pause. .B EINVAL The value in the .I tv_nsec -field was not in the range 0 to 999999999 or +field was not in the range [0, 999999999] or .I tv_sec was negative. .SH STANDARDS
man2/utimensat.2 +1 -1
@@ -272,7 +272,7 @@ Invalid value in .B EINVAL Invalid value in one of the .I tv_nsec -fields (value outside range 0 to 999,999,999, and not +fields (value outside range [0, 999999999], and not .B UTIME_NOW or .BR UTIME_OMIT );
Re: [PATCH v2 03/11] man2/: use consistent closed interval notation for value ranges
Hi Brian,
Quoted 11 lines · Brian Inglis
--- man2/clock_getres.2 | 2 +- man2/clock_nanosleep.2 | 2 +- man2/getitimer.2 | 4 ++-- man2/gettimeofday.2 | 2 +- man2/nanosleep.2 | 4 ++-- man2/utimensat.2 | 2 +- 6 files changed, 8 insertions(+), 8 deletions(-)v2-0003-man2-use-consistent-interval-notation-for-value-r.patch
Patch applied.
Cheers,
Alex
Quoted 97 lines
man2/clock_getres.2 +1
-1@@ -272,7 +272,7 @@ does not refer to a valid instance of a clock object. .I tp.tv_sec is negative or .I tp.tv_nsec -is outside the range [0..999,999,999]. +is outside the range [0, 999,999,999]. .TP .B EINVAL Theman2/clock_nanosleep.2 +1
-1@@ -158,7 +158,7 @@ The sleep was interrupted by a signal handler; see .B EINVAL The value in the .I tv_nsec -field was not in the range 0 to 999999999 or +field was not in the range [0, 999999999] or .I tv_sec was negative. .TPman2/getitimer.2 +2
-2@@ -158,7 +158,7 @@ or (since Linux 2.6.22) one of the .I tv_usec fields in the structure pointed to by .I new_value -contains a value outside the range 0 to 999999. +contains a value outside the range [0, 999999]. .SH STANDARDS POSIX.1-2001, SVr4, 4.4BSD (this call first appeared in 4.2BSD). POSIX.1-2008 marks@@ -253,7 +253,7 @@ POSIX.1-2001 says that .BR setitimer () should fail if a .I tv_usec -value is specified that is outside of the range 0 to 999999. +value is specified that is outside of the range [0, 999999]. 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.man2/gettimeofday.2 +1
-1@@ -152,7 +152,7 @@ is invalid. .I tv.tv_sec is negative or .I tv.tv_usec -is outside the range [0..999,999]. +is outside the range [0, 999999]. .TP .BR EINVAL " (since Linux 4.3)" .\" commit e1d7ba8735551ed79c7a0463a042353574b96da3man2/nanosleep.2 +2
-2@@ -66,7 +66,7 @@ The structure is used to specify intervals of time with nanosecond precision. .PP -The value of the nanoseconds field must be in the range 0 to 999999999. +The value of the nanoseconds field must be in the range [0, 999999999]. .PP Compared to .BR sleep (3)@@ -106,7 +106,7 @@ again and continue with the pause. .B EINVAL The value in the .I tv_nsec -field was not in the range 0 to 999999999 or +field was not in the range [0, 999999999] or .I tv_sec was negative. .SH STANDARDSman2/utimensat.2 +1
-1@@ -272,7 +272,7 @@ Invalid value in .B EINVAL Invalid value in one of the .I tv_nsec -fields (value outside range 0 to 999,999,999, and not +fields (value outside range [0, 999999999], and not .B UTIME_NOW or .BR UTIME_OMIT );
Signature · 2 lines
<http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
PATCH v2 4/11 man2/open.2: punctuate octal perms with digit separators
In reply to Brian Inglis--- man2/open.2 | 32 ++++++++++++++++---------------- 1 file changed, 16 insertions(+), 16 deletions(-)
man2/open.2 +16 -16
@@ -308,40 +308,40 @@ The following symbolic constants are provided for .RS .TP 9 .B S_IRWXU -00700 user (file owner) has read, write, and execute permission +00\[aq]700 user (file owner) has read, write, and execute permission .TP .B S_IRUSR -00400 user has read permission +00\[aq]400 user has read permission .TP .B S_IWUSR -00200 user has write permission +00\[aq]200 user has write permission .TP .B S_IXUSR -00100 user has execute permission +00\[aq]100 user has execute permission .TP .B S_IRWXG -00070 group has read, write, and execute permission +00\[aq]070 group has read, write, and execute permission .TP .B S_IRGRP -00040 group has read permission +00\[aq]040 group has read permission .TP .B S_IWGRP -00020 group has write permission +00\[aq]020 group has write permission .TP .B S_IXGRP -00010 group has execute permission +00\[aq]010 group has execute permission .TP .B S_IRWXO -00007 others have read, write, and execute permission +00\[aq]007 others have read, write, and execute permission .TP .B S_IROTH -00004 others have read permission +00\[aq]004 others have read permission .TP .B S_IWOTH -00002 others have write permission +00\[aq]002 others have write permission .TP .B S_IXOTH -00001 others have execute permission +00\[aq]001 others have execute permission .RE .IP According to POSIX, the effect when other bits are set in
@@ -352,14 +352,14 @@ On Linux, the following bits are also honored in .RS .TP 9 .B S_ISUID -0004000 set-user-ID bit +0\[aq]004\[aq]000 set-user-ID bit .TP .B S_ISGID -0002000 set-group-ID bit (see +0\[aq]002\[aq]000 set-group-ID bit (see .BR inode (7)). .TP .B S_ISVTX -0001000 sticky bit (see +0\[aq]001\[aq]000 sticky bit (see .BR inode (7)). .RE .TP
@@ -1319,7 +1319,7 @@ flags are not specified in POSIX.1-2001, but are specified in POSIX.1-2008. Since glibc 2.12, one can obtain their definitions by defining either .B _POSIX_C_SOURCE -with a value greater than or equal to 200809L or +with a value greater than or equal to 2008\[aq]09L or .B _XOPEN_SOURCE with a value greater than or equal to 700. In glibc 2.11 and earlier, one obtains the definitions by defining
Re: [PATCH v2 04/11] man2/open.2: punctuate octal perms with digit separators
Hi Brian,
Quoted 83 lines · Brian Inglis
--- man2/open.2 | 32 ++++++++++++++++---------------- 1 file changed, 16 insertions(+), 16 deletions(-)v2-0004-man2-open.2-punctuate-octal-perms-with-digit-sepa.patch
man2/open.2 +15
-15@@ -308,40 +308,40 @@ The following symbolic constants are provided for .RS .TP 9 .B S_IRWXU -00700 user (file owner) has read, write, and execute permission +00\[aq]700 user (file owner) has read, write, and execute permission .TP .B S_IRUSR -00400 user has read permission +00\[aq]400 user has read permission .TP .B S_IWUSR -00200 user has write permission +00\[aq]200 user has write permission .TP .B S_IXUSR -00100 user has execute permission +00\[aq]100 user has execute permission .TP .B S_IRWXG -00070 group has read, write, and execute permission +00\[aq]070 group has read, write, and execute permission .TP .B S_IRGRP -00040 group has read permission +00\[aq]040 group has read permission .TP .B S_IWGRP -00020 group has write permission +00\[aq]020 group has write permission .TP .B S_IXGRP -00010 group has execute permission +00\[aq]010 group has execute permission .TP .B S_IRWXO -00007 others have read, write, and execute permission +00\[aq]007 others have read, write, and execute permission .TP .B S_IROTH -00004 others have read permission +00\[aq]004 others have read permission .TP .B S_IWOTH -00002 others have write permission +00\[aq]002 others have write permission .TP .B S_IXOTH -00001 others have execute permission +00\[aq]001 others have execute permission .RE .IP According to POSIX, the effect when other bits are set in@@ -352,14 +352,14 @@ On Linux, the following bits are also honored in .RS .TP 9 .B S_ISUID -0004000 set-user-ID bit +0\[aq]004\[aq]000 set-user-ID bit .TP .B S_ISGID -0002000 set-group-ID bit (see +0\[aq]002\[aq]000 set-group-ID bit (see .BR inode (7)). .TP .B S_ISVTX -0001000 sticky bit (see +0\[aq]001\[aq]000 sticky bit (see .BR inode (7)). .RE .TP
man2/open.2 flags are not specified in POSIX.1-2001, · line 1322
Quoted 5 lines
man2/open.2 +1
-1@@ -1319,7 +1319,7 @@ flags are not specified in POSIX.1-2001, but are specified in POSIX.1-2008. Since glibc 2.12, one can obtain their definitions by defining either .B _POSIX_C_SOURCE -with a value greater than or equal to 200809L or +with a value greater than or equal to 2008\[aq]09L or
This is not an octal :)
Cheers,
Alex
Quoted 3 lines
man2/open.2 +0
-0.B _XOPEN_SOURCE with a value greater than or equal to 700. In glibc 2.11 and earlier, one obtains the definitions by defining
Signature · 2 lines
<http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
PATCH v2 5/11 man2/reboot.2: show BCD dates in hex not decimal
In reply to Brian Inglis--- man2/reboot.2 | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
man2/reboot.2 +4 -4
@@ -51,16 +51,16 @@ equals .I magic2 equals .B LINUX_REBOOT_MAGIC2 -(that is, 672274793). +(that is, 0x28121969). However, since Linux 2.1.17 also .B LINUX_REBOOT_MAGIC2A -(that is, 85072278) +(that is, 0x05121996) and since Linux 2.1.97 also .B LINUX_REBOOT_MAGIC2B -(that is, 369367448) +(that is, 0x16041998) and since Linux 2.5.71 also .B LINUX_REBOOT_MAGIC2C -(that is, 537993216) +(that is, 0x20112000) are permitted as values for .IR magic2 . (The hexadecimal values of these constants are meaningful.)
Re: [PATCH v2 05/11] man2/reboot.2: show BCD dates in hex not decimal
Hi Brian,
On 2/8/23 21:27, Brian Inglis wrote:
Patch applied.
Thanks,
Alex
Quoted 4 lines
--- man2/reboot.2 | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
Signature · 2 lines
<http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
PATCH v2 6/11 man2/reboot.2: punctuate hex in docs with digit separators
In reply to Brian Inglis--- man2/reboot.2 | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-)
man2/reboot.2 +12 -12
@@ -47,20 +47,20 @@ unless .I magic equals .B LINUX_REBOOT_MAGIC1 -(that is, 0xfee1dead) and +(that is, 0xfee1\[aq]dead) and .I magic2 equals .B LINUX_REBOOT_MAGIC2 -(that is, 0x28121969). +(that is 0x2812\[aq]1969). However, since Linux 2.1.17 also .B LINUX_REBOOT_MAGIC2A -(that is, 0x05121996) +(that is 0x0512\[aq]1996) and since Linux 2.1.97 also .B LINUX_REBOOT_MAGIC2B -(that is, 0x16041998) +(that is 0x1604\[aq]1998) and since Linux 2.5.71 also .B LINUX_REBOOT_MAGIC2C -(that is, 0x20112000) +(that is 0x2011\[aq]2000) are permitted as values for .IR magic2 . (The hexadecimal values of these constants are meaningful.)
@@ -81,7 +81,7 @@ proper action (maybe: kill all processes, sync, reboot). .TP .B LINUX_REBOOT_CMD_CAD_ON .RB ( RB_ENABLE_CAD , -0x89abcdef). +0x89ab\[aq]cdef). CAD is enabled. This means that the CAD keystroke will immediately cause the action associated with
@@ -89,7 +89,7 @@ the action associated with .TP .B LINUX_REBOOT_CMD_HALT .RB ( RB_HALT_SYSTEM , -0xcdef0123; since Linux 1.1.76). +0xcdef\[aq]0123; since Linux 1.1.76). The message "System halted." is printed, and the system is halted. Control is given to the ROM monitor, if there is one. If not preceded by a
@@ -98,7 +98,7 @@ data will be lost. .TP .B LINUX_REBOOT_CMD_KEXEC .RB ( RB_KEXEC , -0x45584543, since Linux 2.6.13). +0x4558\[aq]4543; since Linux 2.6.13). Execute a kernel that has been loaded earlier with .BR kexec_load (2). This option is available only if the kernel was configured with
@@ -106,7 +106,7 @@ This option is available only if the kernel was configured with .TP .B LINUX_REBOOT_CMD_POWER_OFF .RB ( RB_POWER_OFF , -0x4321fedc; since Linux 2.1.30). +0x4321\[aq]fedc; since Linux 2.1.30). The message "Power down." is printed, the system is stopped, and all power is removed from the system, if possible. If not preceded by a
@@ -115,7 +115,7 @@ data will be lost. .TP .B LINUX_REBOOT_CMD_RESTART .RB ( RB_AUTOBOOT , -0x1234567). +0x0123\[aq]4567). The message "Restarting system." is printed, and a default restart is performed immediately. If not preceded by a
@@ -123,7 +123,7 @@ If not preceded by a data will be lost. .TP .B LINUX_REBOOT_CMD_RESTART2 -(0xa1b2c3d4; since Linux 2.1.30). +(0xa1b2\[aq]c3d4; since Linux 2.1.30). The message "Restarting system with command \(aq%s\(aq" is printed, and a restart (using the command string given in .IR arg )
@@ -134,7 +134,7 @@ data will be lost. .TP .B LINUX_REBOOT_CMD_SW_SUSPEND .RB ( RB_SW_SUSPEND , -0xd000fce1; since Linux 2.5.18). +0xd000\[aq]fce1; since Linux 2.5.18). The system is suspended (hibernated) to disk. This option is available only if the kernel was configured with .BR CONFIG_HIBERNATION .
PATCH v2 7/11 man2/statfs.2: punctuate hex in docs with digit separators
In reply to Brian Inglis--- man2/statfs.2 | 110 +++++++++++++++++++++++++------------------------- 1 file changed, 55 insertions(+), 55 deletions(-)
man2/statfs.2 +55 -55
@@ -58,90 +58,90 @@ The following filesystem types may appear in .EX ADFS_SUPER_MAGIC 0xadf5 AFFS_SUPER_MAGIC 0xadff -AFS_SUPER_MAGIC 0x5346414f -ANON_INODE_FS_MAGIC 0x09041934 /* Anonymous inode FS (for +AFS_SUPER_MAGIC 0x5346\[aq]414f +ANON_INODE_FS_MAGIC 0x0904\[aq]1934 /* Anonymous inode FS (for pseudofiles that have no name; e.g., epoll, signalfd, bpf) */ AUTOFS_SUPER_MAGIC 0x0187 -BDEVFS_MAGIC 0x62646576 -BEFS_SUPER_MAGIC 0x42465331 -BFS_MAGIC 0x1badface -BINFMTFS_MAGIC 0x42494e4d -BPF_FS_MAGIC 0xcafe4a11 -BTRFS_SUPER_MAGIC 0x9123683e -BTRFS_TEST_MAGIC 0x73727279 -CGROUP_SUPER_MAGIC 0x27e0eb /* Cgroup pseudo FS */ -CGROUP2_SUPER_MAGIC 0x63677270 /* Cgroup v2 pseudo FS */ -CIFS_MAGIC_NUMBER 0xff534d42 -CODA_SUPER_MAGIC 0x73757245 -COH_SUPER_MAGIC 0x012ff7b7 -CRAMFS_MAGIC 0x28cd3d45 -DEBUGFS_MAGIC 0x64626720 +BDEVFS_MAGIC 0x6264\[aq]6576 +BEFS_SUPER_MAGIC 0x4246\[aq]5331 +BFS_MAGIC 0x1bad\[aq]face +BINFMTFS_MAGIC 0x4249\[aq]4e4d +BPF_FS_MAGIC 0xcafe\[aq]4a11 +BTRFS_SUPER_MAGIC 0x9123\[aq]683e +BTRFS_TEST_MAGIC 0x7372\[aq]7279 +CGROUP_SUPER_MAGIC 0x27\[aq]e0eb /* Cgroup pseudo FS */ +CGROUP2_SUPER_MAGIC 0x6367\[aq]7270 /* Cgroup v2 pseudo FS */ +CIFS_MAGIC_NUMBER 0xff53\[aq]4d42 +CODA_SUPER_MAGIC 0x7375\[aq]7245 +COH_SUPER_MAGIC 0x012f\[aq]f7b7 +CRAMFS_MAGIC 0x28cd\[aq]3d45 +DEBUGFS_MAGIC 0x6462\[aq]6720 DEVFS_SUPER_MAGIC 0x1373 /* Linux 2.6.17 and earlier */ DEVPTS_SUPER_MAGIC 0x1cd1 ECRYPTFS_SUPER_MAGIC 0xf15f -EFIVARFS_MAGIC 0xde5e81e4 -EFS_SUPER_MAGIC 0x00414a53 +EFIVARFS_MAGIC 0xde5e\[aq]81e4 +EFS_SUPER_MAGIC 0x0041\[aq]4a53 EXT_SUPER_MAGIC 0x137d /* Linux 2.0 and earlier */ EXT2_OLD_SUPER_MAGIC 0xef51 EXT2_SUPER_MAGIC 0xef53 EXT3_SUPER_MAGIC 0xef53 EXT4_SUPER_MAGIC 0xef53 -F2FS_SUPER_MAGIC 0xf2f52010 -FUSE_SUPER_MAGIC 0x65735546 -FUTEXFS_SUPER_MAGIC 0xbad1dea /* Unused */ +F2FS_SUPER_MAGIC 0xf2f5\[aq]2010 +FUSE_SUPER_MAGIC 0x6573\[aq]5546 +FUTEXFS_SUPER_MAGIC 0xbad\[aq]1dea /* Unused */ HFS_SUPER_MAGIC 0x4244 -HOSTFS_SUPER_MAGIC 0x00c0ffee -HPFS_SUPER_MAGIC 0xf995e849 -HUGETLBFS_MAGIC 0x958458f6 +HOSTFS_SUPER_MAGIC 0x00c0\[aq]ffee +HPFS_SUPER_MAGIC 0xf995\[aq]e849 +HUGETLBFS_MAGIC 0x9584\[aq]58f6 ISOFS_SUPER_MAGIC 0x9660 JFFS2_SUPER_MAGIC 0x72b6 -JFS_SUPER_MAGIC 0x3153464a +JFS_SUPER_MAGIC 0x3153\[aq]464a MINIX_SUPER_MAGIC 0x137f /* original minix FS */ MINIX_SUPER_MAGIC2 0x138f /* 30 char minix FS */ MINIX2_SUPER_MAGIC 0x2468 /* minix V2 FS */ MINIX2_SUPER_MAGIC2 0x2478 /* minix V2 FS, 30 char names */ MINIX3_SUPER_MAGIC 0x4d5a /* minix V3 FS, 60 char names */ -MQUEUE_MAGIC 0x19800202 /* POSIX message queue FS */ +MQUEUE_MAGIC 0x1980\[aq]0202 /* POSIX message queue FS */ MSDOS_SUPER_MAGIC 0x4d44 -MTD_INODE_FS_MAGIC 0x11307854 +MTD_INODE_FS_MAGIC 0x1130\[aq]7854 NCP_SUPER_MAGIC 0x564c NFS_SUPER_MAGIC 0x6969 NILFS_SUPER_MAGIC 0x3434 -NSFS_MAGIC 0x6e736673 -NTFS_SB_MAGIC 0x5346544e -OCFS2_SUPER_MAGIC 0x7461636f +NSFS_MAGIC 0x6e73\[aq]6673 +NTFS_SB_MAGIC 0x5346\[aq]544e +OCFS2_SUPER_MAGIC 0x7461\[aq]636f OPENPROM_SUPER_MAGIC 0x9fa1 -OVERLAYFS_SUPER_MAGIC 0x794c7630 -PIPEFS_MAGIC 0x50495045 +OVERLAYFS_SUPER_MAGIC 0x794c\[aq]7630 +PIPEFS_MAGIC 0x5049\[aq]5045 PROC_SUPER_MAGIC 0x9fa0 /* /proc FS */ -PSTOREFS_MAGIC 0x6165676c +PSTOREFS_MAGIC 0x6165\[aq]676c QNX4_SUPER_MAGIC 0x002f -QNX6_SUPER_MAGIC 0x68191122 -RAMFS_MAGIC 0x858458f6 -REISERFS_SUPER_MAGIC 0x52654973 +QNX6_SUPER_MAGIC 0x6819\[aq]1122 +RAMFS_MAGIC 0x8584\[aq]58f6 +REISERFS_SUPER_MAGIC 0x5265\[aq]4973 ROMFS_MAGIC 0x7275 -SECURITYFS_MAGIC 0x73636673 -SELINUX_MAGIC 0xf97cff8c -SMACK_MAGIC 0x43415d53 +SECURITYFS_MAGIC 0x7363\[aq]6673 +SELINUX_MAGIC 0xf97c\[aq]ff8c +SMACK_MAGIC 0x4341\[aq]5d53 SMB_SUPER_MAGIC 0x517b -SMB2_MAGIC_NUMBER 0xfe534d42 -SOCKFS_MAGIC 0x534f434b -SQUASHFS_MAGIC 0x73717368 -SYSFS_MAGIC 0x62656572 -SYSV2_SUPER_MAGIC 0x012ff7b6 -SYSV4_SUPER_MAGIC 0x012ff7b5 -TMPFS_MAGIC 0x01021994 -TRACEFS_MAGIC 0x74726163 -UDF_SUPER_MAGIC 0x15013346 -UFS_MAGIC 0x00011954 +SMB2_MAGIC_NUMBER 0xfe53\[aq]4d42 +SOCKFS_MAGIC 0x534f\[aq]434b +SQUASHFS_MAGIC 0x7371\[aq]7368 +SYSFS_MAGIC 0x6265\[aq]6572 +SYSV2_SUPER_MAGIC 0x012f\[aq]f7b6 +SYSV4_SUPER_MAGIC 0x012f\[aq]f7b5 +TMPFS_MAGIC 0x0102\[aq]1994 +TRACEFS_MAGIC 0x7472\[aq]6163 +UDF_SUPER_MAGIC 0x1501\[aq]3346 +UFS_MAGIC 0x0001\[aq]1954 USBDEVICE_SUPER_MAGIC 0x9fa2 -V9FS_MAGIC 0x01021997 -VXFS_SUPER_MAGIC 0xa501fcf5 -XENFS_SUPER_MAGIC 0xabba1974 -XENIX_SUPER_MAGIC 0x012ff7b4 -XFS_SUPER_MAGIC 0x58465342 -_XIAFS_SUPER_MAGIC 0x012fd16d /* Linux 2.0 and earlier */ +V9FS_MAGIC 0x0102\[aq]1997 +VXFS_SUPER_MAGIC 0xa501\[aq]fcf5 +XENFS_SUPER_MAGIC 0xabba\[aq]1974 +XENIX_SUPER_MAGIC 0x012f\[aq]f7b4 +XFS_SUPER_MAGIC 0x5846\[aq]5342 +_XIAFS_SUPER_MAGIC 0x012f\[aq]d16d /* Linux 2.0 and earlier */ .EE .in .PP
PATCH v2 8/11 man2/adjtimex.2: use ISO/IEC multiple symbols and digit separators in ranges and example docs
In reply to Brian Inglis--- man2/adjtimex.2 | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
man2/adjtimex.2 +6 -6
@@ -108,7 +108,7 @@ Set frequency offset from .IR buf.freq . Since Linux 2.6.26, .\" commit 074b3b87941c99bc0ce35385b5817924b1ed0c23 -the supplied value is clamped to the range (\-32768000, +32768000). +the supplied value is clamped to the range (\-32\[aq]000Ki, +32\[aq]000Ki). In older kernels, an .B EINVAL error occurs if the supplied value is out of range.
@@ -471,7 +471,7 @@ does not point to writable memory. .BR EINVAL " (before Linux 2.6.26)" An attempt was made to set .I buf.freq -to a value outside the range (\-33554432, +33554432). +to a value outside the range (\-32Mi, +32Mi). .\" From a quick glance, it appears there was no clamping or range check .\" for buf.freq before Linux 2.0 .TP
@@ -479,8 +479,8 @@ to a value outside the range (\-33554432, +33554432). An attempt was made to set .I buf.offset to a value outside the permitted range. -Before Linux 2.0, the permitted range was (\-131072, +131072). -From Linux 2.0 onwards, the permitted range was (\-512000, +512000). +Before Linux 2.0, the permitted range was (\-128Ki, +128Ki). +From Linux 2.0 onwards, the permitted range was (\-512k, +512k). .TP .B EINVAL An attempt was made to set
@@ -505,9 +505,9 @@ for a discussion of dynamic clocks. An attempt was made to set .I buf.tick to a value outside the range -.RB 900000/ HZ +.RB 900k/ HZ to -.RB 1100000/ HZ , +.RB 1\[aq]100k/ HZ , where .B HZ is the system timer interrupt frequency.
PATCH v2 9/11 man2/getrandom.2: change limit to use IEC multiple symbol
In reply to Brian Inglis--- man2/getrandom.2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
man2/getrandom.2 +1 -1
@@ -188,7 +188,7 @@ As of Linux 3.19 the following limits apply: .IP \(bu 3 When reading from the .I urandom -source, a maximum of 33554431 bytes is returned by a single call to +source, a maximum of 32Mi-1 bytes is returned by a single call to .BR getrandom () on systems where .I int
Re: [PATCH v2 09/11] man2/getrandom.2: change limit to use IEC multiple symbol
Hi Brian,
On 2/8/23 21:27, Brian Inglis wrote:
Patch applied.
Thanks,
Alex
Quoted 4 lines
--- man2/getrandom.2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Signature · 2 lines
<http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
PATCH v2 10/11 man2/futex.2: change limit to use ISO multiple symbol
In reply to Brian Inglis--- man2/futex.2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
man2/futex.2 +1 -1
@@ -1536,7 +1536,7 @@ argument was invalid .RI ( tv_sec was less than zero, or .I tv_nsec -was not less than 1,000,000,000). +was not less than 1G). .TP .B EINVAL The operation specified in
Re: [PATCH v2 10/11] man2/futex.2: change limit to use ISO multiple symbol
Hi Brian,
Quoted 12 lines · Brian Inglis
--- man2/futex.2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)v2-0010-man2-futex.2-change-limit-to-use-ISO-suffix.patch
man2/futex.2 +0
-0
man2/futex.2 argument was invalid · line 1539
Quoted 5 lines
man2/futex.2 +1
-1@@ -1536,7 +1536,7 @@ argument was invalid .RI ( tv_sec was less than zero, or .I tv_nsec -was not less than 1,000,000,000). +was not less than 1G).
For nanoseconds, I think 1G is a bit weird. Since you cant say 1 Gns, I'd rather keep the value. Anyway, 1_000_000_000 or 1'000'000'000, or whatever separator we use) is something quite readable in the context of nanoseconds.
Cheers,
Alex
Quoted 3 lines
man2/futex.2 +0
-0.TP .B EINVAL The operation specified in
Signature · 2 lines
<http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
Re: [PATCH v2 10/11] man2/futex.2: change limit to use ISO multiple symbol
Quoted 10 lines · Alejandro Colomar
Hi Brian,
Quoted 7 lines · Brian Inglis
--- man2/futex.2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)v2-0010-man2-futex.2-change-limit-to-use-ISO-suffix.patch
Quoted 12 lines
man2/futex.2 argument was invalid · line 1539
Quoted 10 lines
man2/futex.2 +1
-1@@ -1536,7 +1536,7 @@ argument was invalid .RI ( tv_sec was less than zero, or .I tv_nsec -was not less than 1,000,000,000). +was not less than 1G).For nanoseconds, I think 1G is a bit weird. Since you cant say 1 Gns, I'd rather keep the value. Anyway, 1_000_000_000 or 1'000'000'000, or whatever separator we use) is something quite readable in the context of nanoseconds.
SI actually allows Gns (/nGs?) and they cancel to s, but either looks weird here, so okay if you don't like the G in text and want to keep the long form. [I was used to the UK(/EU?) (electronics?) convention of using the SI prefix instead of a decimal point e.g. 3k6s 31M536s etc. so not much looks off to me.]
Signature · 6 lines
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut -- Antoine de Saint-Exupéry
Re: [PATCH v2 10/11] man2/futex.2: change limit to use ISO multiple symbol
* Brian Inglis <[email protected]>, 2023-02-08 15:33:
Quoted 4 lines
Quoted 4 lines
man2/futex.2 argument was invalid · line 1539
Quoted 2 lines
man2/futex.2 +1
-1-was not less than 1,000,000,000). +was not less than 1G).For nanoseconds, I think 1G is a bit weird.
Not only weird, but also not allowed by SI. From the brochure: "Prefix symbols can neither stand alone nor be attached to the number 1".
Quoted 1 line
SI actually allows Gns (/nGs?)
Nope: "Compound prefix symbols, i.e. prefix symbols formed by the juxtaposition of two or more prefix symbols, are not permitted."
Signature · 1 line
Jakub Wilk
Re: [PATCH v2 10/11] man2/futex.2: change limit to use ISO multiple symbol
Hi Jakub!
Quoted 8 lines · Jakub Wilk
* Brian Inglis <[email protected]>, 2023-02-08 15:33:
Quoted 4 lines
Quoted 4 lines
man2/futex.2 argument was invalid · line 1539
Quoted 2 lines
man2/futex.2 +1
-1-was not less than 1,000,000,000). +was not less than 1G).For nanoseconds, I think 1G is a bit weird.
Not only weird, but also not allowed by SI. From the brochure: "Prefix symbols can neither stand alone nor be attached to the number 1".
That's in section 5.4.7 of the SI Brochure (v9) for those who don't have the context. However, that section not only forbids 1G, but also 32G or 32Mi. The point is that you can't attach a prefix to a number without units, because it's a prefix rather than a suffix. According to the SI, one would have to express that as powers of 10 (or the expanded number if you prefer).
However, since in the case of 32Mi-1, which is 33554431, which is 32 * 2^20 - 1, which is 2^25-1, the most readable version is 32Mi-1, I'm willing to make an exception an divert the SI in that regards.
If someone is familiar with ISO/IEC 80000-1 and could check if it allows that, it would be nice to know.
But in this case, we have a unit, which is seconds, and we're already multiplying it by nano, so G doesn't fit in the rule below.
Quoted 5 lines
Quoted 2 lines
SI actually allows Gns (/nGs?)
Nope: "Compound prefix symbols, i.e. prefix symbols formed by the juxtaposition of two or more prefix symbols, are not permitted."
Thanks for finding the right quotation. That was my understanding, but couldn't find it.
This rule I'd rather follow.
Cheers,
Alex
Quoted 1 line
Signature · 2 lines
<http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
Re: [PATCH v2 10/11] man2/futex.2: change limit to use ISO multiple symbol
Quoted 11 lines · Alejandro Colomar
Quoted 8 lines · Jakub Wilk
* Brian Inglis, 2023-02-08 15:33:
Quoted 4 lines
Quoted 4 lines
man2/futex.2 argument was invalid · line 1539
Quoted 2 lines
man2/futex.2 +1
-1-was not less than 1,000,000,000). +was not less than 1G).For nanoseconds, I think 1G is a bit weird.
Not only weird, but also not allowed by SI. From the brochure: "Prefix symbols can neither stand alone nor be attached to the number 1".
That's in section 5.4.7 of the SI Brochure (v9) for those who don't have the context. However, that section not only forbids 1G, but also 32G or 32Mi. The point is that you can't attach a prefix to a number without units, because it's a prefix rather than a suffix. According to the SI, one would have to express that as powers of 10 (or the expanded number if you prefer).
That's commonly accepted, and we are not writing scientific papers, we are producing docs for comsumption by international English readers, where many native speakers may actually be less familiar with metric units and SI conventions. [In those financial and management areas M = 1k and MM = 1M!
And I do cringe at such common usages as 1,000kg for tonne or 1,000km for 1Mm, where nobody has problems with MJ/GJ/PJ for gas energy or MW/GW/PW for electrical power in their monthly bills!]
Quoted 3 lines
However, since in the case of 32Mi-1, which is 33554431, which is 32 * 2^20 - 1, which is 2^25-1, the most readable version is 32Mi-1, I'm willing to make an exception an divert the SI in that regards.
If someone is familiar with ISO/IEC 80000-1 and could check if it allows that, it would be nice to know.
The following is available online (more recent is not publicly available between 3. Normative References and Bibliography - To view...click on the "Buy" button. even for the original 80000-13:2008 Information science and technology):
https://www.iso.org/obp/ui/#iso:std:iso:80000:-1:ed-1:v1:en
"3.8
quantity of dimension one
dimensionless quantity
quantity for which all the exponents of the factors corresponding to the base quantities in its quantity dimension are zero
Note 1 to entry: The term “dimensionless quantity” is commonly used and is kept here for historical reasons. It stems from the fact that all exponents are zero in the symbolic representation of the dimension for such quantities. The term “quantity of dimension one” reflects the convention in which the symbolic representation of the dimension for such quantities is the symbol 1, see Clause 5. This dimension is not a number, but the neutral element for multiplication of dimensions. Note 2 to entry: The measurement units and values of quantities of dimension one are numbers, but such quantities convey more information than a number.
Note 3 to entry: Some quantities of dimension one are defined as the ratios of two quantities of the same kind. The coherent derived unit is the number one, symbol 1.
EXAMPLE
Plane angle, solid angle, refractive index, relative permeability, mass fraction, friction factor, Mach number. Note 4 to entry: Numbers of entities are quantities of dimension one.
EXAMPLE
Number of turns in a coil, number of molecules in a given sample, degeneracy of the energy levels of a quantum system.
Note 5 to entry: Adapted from ISO/IEC Guide 99:2007, definition 1.8, in which Notes 1 and 3 are different and in which “dimensionless quantity” is given as an admitted term."
https://www.iso.org/obp/ui/#iso:std:iso-iec:guide:99:ed-1:v2:en
"1.8 (1.6)
quantity of dimension one
dimensionless quantity
quantity for which all the exponents of the factors corresponding to the base quantities in its quantity dimension are zero
Note 1 to entry: The term “dimensionless quantity” is commonly used and is kept here for historical reasons. It stems from the fact that all exponents are zero in the symbolic representation of the dimension for such quantities. The term “quantity of dimension one” reflects the convention in which the symbolic representation of the dimension for such quantities is the symbol 1 (see ISO 31-0:1992, 2.2.6). Note 2 to entry: The measurement units and values of quantities of dimension one are numbers, but such quantities convey more information than a number.
Note 3 to entry: Some quantities of dimension one are defined as the ratios of two quantities of the same kind.
EXAMPLE 1:Plane angle, solid angle, refractive index, relative permeability, mass fraction, friction factor, Mach number.
Note 4 to entry: Numbers of entities are quantities of dimension one.
EXAMPLE 2:Number of turns in a coil, number of molecules in a given sample, degeneracy of the energy levels of a quantum system."
Quoted 5 lines
But in this case, we have a unit, which is seconds, and we're already multiplying it by nano, so G doesn't fit in the rule below.
Quoted 3 lines
Quoted 1 line
SI actually allows Gns (/nGs?)
Nope: "Compound prefix symbols, i.e. prefix symbols formed by the juxtaposition of two or more prefix symbols, are not permitted."
May have been more flexible when introduced or in another metric system [vulgar fractions, GCD, LCM, and variable radix arithmetic were standard in my primary school - L/s/d - t/cwt/st/lb/oz - mi/fl/ch/rod/yd/ft/in - as was CGS when we got to decimal fractions ;^> ]
Quoted 2 lines
Thanks for finding the right quotation. That was my understanding, but couldn't find it. This rule I'd rather follow.
No problem - would add confusion for non-metric types.
Signature · 6 lines
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut -- Antoine de Saint-Exupéry
PATCH v2 11/11 man2/: punctuate long numeric strings with digit separators
In reply to Brian Inglis--- man2/add_key.2 | 2 +- man2/clock_getres.2 | 2 +- man2/clock_nanosleep.2 | 2 +- man2/eventfd.2 | 6 +++--- man2/execve.2 | 2 +- man2/fcntl.2 | 4 ++-- man2/getitimer.2 | 4 ++-- man2/gettimeofday.2 | 2 +- man2/ioctl.2 | 4 ++-- man2/ioctl_console.2 | 2 +- man2/ioctl_getfsmap.2 | 4 ++-- man2/ioperm.2 | 2 +- man2/kexec_load.2 | 2 +- man2/link.2 | 4 ++-- man2/msgget.2 | 2 +- man2/nanosleep.2 | 4 ++-- man2/pciconfig_read.2 | 2 +- man2/perf_event_open.2 | 2 +- man2/personality.2 | 8 ++++---- man2/prctl.2 | 2 +- man2/read.2 | 2 +- man2/semget.2 | 4 ++-- man2/sendfile.2 | 2 +- man2/shmget.2 | 2 +- man2/sigaction.2 | 4 ++-- man2/spu_run.2 | 8 ++++---- man2/statx.2 | 2 +- man2/syscall.2 | 2 +- man2/timer_settime.2 | 4 ++-- man2/timerfd_create.2 | 2 +- man2/truncate.2 | 4 ++-- man2/utimensat.2 | 6 +++--- man2/write.2 | 2 +- 33 files changed, 53 insertions(+), 53 deletions(-)
man2/add_key.2 +1 -1
@@ -110,7 +110,7 @@ This is a general purpose key type whose payload may be read and updated by user-space applications. The key is kept entirely within kernel memory. The payload for keys of this type is a blob of arbitrary data -of up to 32,767 bytes. +of up to 32\[aq]767 bytes. .TP .IR """logon""" " (since Linux 3.3)" .\" commit 9f6ed2ca257fa8650b876377833e6f14e272848b
man2/clock_getres.2 +1 -1
@@ -272,7 +272,7 @@ does not refer to a valid instance of a clock object. .I tp.tv_sec is negative or .I tp.tv_nsec -is outside the range [0, 999,999,999]. +is outside the range [0, 999\[aq]999\[aq]999]. .TP .B EINVAL The
man2/clock_nanosleep.2 +1 -1
@@ -158,7 +158,7 @@ The sleep was interrupted by a signal handler; see .B EINVAL The value in the .I tv_nsec -field was not in the range [0, 999999999] or +field was not in the range [0, 999\[aq]999\[aq]999] or .I tv_sec was negative. .TP
man2/eventfd.2 +3 -3
@@ -124,7 +124,7 @@ A call adds the 8-byte integer value supplied in its buffer to the counter. The maximum value that may be stored in the counter is the largest -unsigned 64-bit value minus 1 (i.e., 0xfffffffffffffffe). +unsigned 64-bit value minus 1 (i.e., 0xffff\[aq]ffff\[aq]ffff\[aq]fffe). If the addition would cause the counter's value to exceed the maximum, then the .BR write (2)
@@ -140,7 +140,7 @@ A fails with the error .B EINVAL if the size of the supplied buffer is less than 8 bytes, -or if an attempt is made to write the value 0xffffffffffffffff. +or if an attempt is made to write the value 0xffff\[aq]ffff\[aq]ffff\[aq]ffff. .TP .BR poll "(2), " select "(2) (and similar)" The returned file descriptor supports
@@ -190,7 +190,7 @@ If an overflow has occurred, then .BR read (2) will return that maximum .I uint64_t -value (i.e., 0xffffffffffffffff). +value (i.e., 0xffff\[aq]ffff\[aq]ffff\[aq]ffff). .RE .IP The eventfd file descriptor also supports the other file-descriptor
man2/execve.2 +1 -1
@@ -429,7 +429,7 @@ environment space as was provided by Linux 2.6.22 and earlier. (This guarantee was not provided in Linux 2.6.23 and 2.6.24.) Additionally, the limit per string is 32 pages (the kernel constant .BR MAX_ARG_STRLEN ), -and the maximum number of strings is 0x7FFFFFFF. +and the maximum number of strings is 0x7fff\[aq]ffff. .SH RETURN VALUE On success, .BR execve ()
man2/fcntl.2 +2 -2
@@ -1833,13 +1833,13 @@ are specified in POSIX.1-2001. .B _XOPEN_SOURCE with the value 500 or greater, or .B _POSIX_C_SOURCE -with the value 200809L or greater.) +with the value 2008\[aq]09L or greater.) .PP .B F_DUPFD_CLOEXEC is specified in POSIX.1-2008. (To get this definition, define .B _POSIX_C_SOURCE -with the value 200809L or greater, or +with the value 2008\[aq]09L or greater, or .B _XOPEN_SOURCE with the value 700 or greater.) .PP
man2/getitimer.2 +2 -2
@@ -158,7 +158,7 @@ or (since Linux 2.6.22) one of the .I tv_usec fields in the structure pointed to by .I new_value -contains a value outside the range [0, 999999]. +contains a value outside the range [0, 999\[aq]999]. .SH STANDARDS POSIX.1-2001, SVr4, 4.4BSD (this call first appeared in 4.2BSD). POSIX.1-2008 marks
@@ -253,7 +253,7 @@ POSIX.1-2001 says that .BR setitimer () should fail if a .I tv_usec -value is specified that is outside of the range [0, 999999]. +value is specified that is outside of the range [0, 999\[aq]999]. 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.
man2/gettimeofday.2 +1 -1
@@ -152,7 +152,7 @@ is invalid. .I tv.tv_sec is negative or .I tv.tv_usec -is outside the range [0, 999999]. +is outside the range [0, 999\[aq]999]. .TP .BR EINVAL " (since Linux 4.3)" .\" commit e1d7ba8735551ed79c7a0463a042353574b96da3
man2/ioctl.2 +2 -2
@@ -134,9 +134,9 @@ one or more ASCII letters were used. For example, .B TCGETS has value -0x00005401, with 0x54 = \(aqT\(aq indicating the terminal driver, and +0x00\[aq]00\[aq]54\[aq]01, with 0x54 = \(aqT\(aq indicating the terminal driver, and .B CYGETTIMEOUT -has value 0x00435906, with 0x43 0x59 = \(aqC\(aq \(aqY\(aq +has value 0x00\[aq]43\[aq]59\[aq]06, with 0x43 0x59 = \(aqC\(aq \(aqY\(aq indicating the cyclades driver. .PP Later (0.98p5) some more information was built into the number.
man2/ioctl_console.2 +1 -1
@@ -143,7 +143,7 @@ The lower 16 bits of specify the period in clock cycles (that is, .I argp -= 1193180/frequency). += 1\[aq]193\[aq]180/frequency). .I argp = 0 turns sound off. In either case, control returns immediately.
man2/ioctl_getfsmap.2 +2 -2
@@ -112,9 +112,9 @@ A filesystem that can share blocks between files likely requires the tuple to uniquely index any filesystem mapping record. Classic non-sharing filesystems might be able to identify any record with only .RI "(" "device" ", " "physical" ", " "flags" ")." -For example, if the low key is set to (8:0, 36864, 0, 0, 0), the filesystem will +For example, if the low key is set to (8:0, 36\[aq]864, 0, 0, 0), the filesystem will only return records for extents starting at or above 36\ KiB on disk. -If the high key is set to (8:0, 1048576, 0, 0, 0), +If the high key is set to (8:0, 1\[aq]048\[aq]576, 0, 0, 0), only records below 1\ MiB will be returned. The format of .I fmr_device
man2/ioperm.2 +1 -1
@@ -46,7 +46,7 @@ For more ports, the system call had to be used (with a .I level argument of 3). -Since Linux 2.6.8, 65,536 I/O ports can be specified. +Since Linux 2.6.8, 65\[aq]536 I/O ports can be specified. .PP Permissions are inherited by the child created by .BR fork (2)
man2/kexec_load.2 +1 -1
@@ -67,7 +67,7 @@ and is effective only if .I nr_segments is greater than 0. .PP -The high-order bits (corresponding to the mask 0xffff0000) of +The high-order bits (corresponding to the mask 0xffff\[aq]0000) of .I flags contain the architecture of the to-be-executed kernel. Specify (OR) the constant
man2/link.2 +2 -2
@@ -204,9 +204,9 @@ For example, on an .BR ext4 (5) filesystem that does not employ the .I dir_index -feature, the limit on the number of hard links to a file is 65,000; on +feature, the limit on the number of hard links to a file is 65\[aq]000; on .BR btrfs (5), -the limit is 65,535 links. +the limit is 65\[aq]535 links. .TP .B ENAMETOOLONG .IR oldpath " or " newpath " was too long."
man2/msgget.2 +1 -1
@@ -190,7 +190,7 @@ Before Linux 3.19, .\" commit 0050ee059f7fc86b1df2527aaa14ed5dc72f9973 the default value for this limit was calculated using a formula based on available system memory. -Since Linux 3.19, the default value is 32,000. +Since Linux 3.19, the default value is 32\[aq]000. On Linux, this limit can be read and modified via .IR /proc/sys/kernel/msgmni . .SS Linux notes
man2/nanosleep.2 +2 -2
@@ -66,7 +66,7 @@ The structure is used to specify intervals of time with nanosecond precision. .PP -The value of the nanoseconds field must be in the range [0, 999999999]. +The value of the nanoseconds field must be in the range [0, 999\[aq]999\[aq]999]. .PP Compared to .BR sleep (3)
@@ -106,7 +106,7 @@ again and continue with the pause. .B EINVAL The value in the .I tv_nsec -field was not in the range [0, 999999999] or +field was not in the range [0, 999\[aq]999\[aq]999] or .I tv_sec was negative. .SH STANDARDS
man2/pciconfig_read.2 +1 -1
@@ -50,7 +50,7 @@ value. .TP .BR pciconfig_iobase () You pass it a bus/devfn pair and get a physical address for either the -memory offset (for things like prep, this is 0xc0000000), +memory offset (for things like prep, this is 0xc000\[aq]0000), the IO base for PIO cycles, or the ISA holes if any. .SH RETURN VALUE .TP
man2/perf_event_open.2 +1 -1
@@ -3364,7 +3364,7 @@ Setting this too high can allow users to sample at a rate that impacts overall machine performance and potentially lock up the machine. The default value is -100000 (samples per second). +100\[aq]000 (samples per second). .TP .I /proc/sys/kernel/perf_event_max_stack .\" Introduced in c5dfd78eb79851e278b7973031b9ca363da87a7e
man2/personality.2 +4 -4
@@ -34,13 +34,13 @@ UNIX-like operating systems. If .I persona is not -0xffffffff, then +0xffff\[aq]ffff, then .BR personality () sets the caller's execution domain to the value specified by .IR persona . Specifying .I persona -as 0xffffffff provides a way of retrieving +as 0xffff\[aq]ffff provides a way of retrieving the current persona without changing it. .PP A list of the available execution domains can be found in
@@ -63,10 +63,10 @@ With this flag set, disable address-space-layout randomization. Limit the address space to 32 bits. .TP .BR ADDR_LIMIT_3GB " (since Linux 2.4.0)" -With this flag set, use 0xc0000000 as the offset at which to search +With this flag set, use 0xc000\[aq]0000 as the offset at which to search a virtual memory chunk on .BR mmap (2); -otherwise use 0xffffe000. +otherwise use 0xffff\[aq]e000. .TP .BR FDPIC_FUNCPTRS " (since Linux 2.6.11)" User-space function pointers to signal handlers point
man2/prctl.2 +1 -1
@@ -1932,7 +1932,7 @@ The "default" value can't be changed. The timer slack values of .I init (PID 1), the ancestor of all processes, -are 50,000 nanoseconds (50 microseconds). +are 50\[aq]000 nanoseconds (50 microseconds). The timer slack value is inherited by a child created via .BR fork (2), and is preserved across
man2/read.2 +1 -1
@@ -176,7 +176,7 @@ unsigned and signed integer data types specified by POSIX.1. On Linux, .BR read () (and similar system calls) will transfer at most -0x7ffff000 (2,147,479,552) bytes, +0x7fff\[aq]f000 (2\[aq]147\[aq]479\[aq]552) bytes, returning the number of bytes actually transferred. .\" commit e28cc71572da38a5a12c1cfe4d7032017adccf69 (This is true on both 32-bit and 64-bit systems.)
man2/semget.2 +2 -2
@@ -249,7 +249,7 @@ Before Linux 3.19, the default value for this limit was 128. Since Linux 3.19, .\" commit e843e7d2c88b7db107a86bd2c7145dc715c058f4 -the default value is 32,000. +the default value is 32\[aq]000. On Linux, this limit can be read and modified via the fourth field of .IR /proc/sys/kernel/sem . .\" This /proc file is not available in Linux 2.2 and earlier -- MTK
@@ -260,7 +260,7 @@ Before Linux 3.19, the default value for this limit was 250. Since Linux 3.19, .\" commit e843e7d2c88b7db107a86bd2c7145dc715c058f4 -the default value is 32,000. +the default value is 32\[aq]000. On Linux, this limit can be read and modified via the first field of .IR /proc/sys/kernel/sem . .TP
man2/sendfile.2 +1 -1
@@ -179,7 +179,7 @@ with different semantics and prototypes. It should not be used in portable programs. .SH NOTES .BR sendfile () -will transfer at most 0x7ffff000 (2,147,479,552) bytes, +will transfer at most 0x7fff\[aq]f000 (2\[aq]147\[aq]479\[aq]552) bytes, returning the number of bytes actually transferred. .\" commit e28cc71572da38a5a12c1cfe4d7032017adccf69 (This is true on both 32-bit and 64-bit systems.)
man2/shmget.2 +1 -1
@@ -354,7 +354,7 @@ for a discussion of why this default value (rather than is used. .IP From Linux 2.2 up to Linux 3.15, the default value of -this limit was 0x2000000 (32\ MiB). +this limit was 0x200\[aq]0000 (32\ MiB). .IP Because it is not possible to map just part of a shared memory segment, the amount of virtual memory places another limit on the maximum size of a
man2/sigaction.2 +2 -2
@@ -52,7 +52,7 @@ Feature Test Macro Requirements for glibc (see .PP .IR siginfo_t : .nf - _POSIX_C_SOURCE >= 199309L + _POSIX_C_SOURCE >= 1993\[aq]09L .fi .SH DESCRIPTION The
@@ -623,7 +623,7 @@ and or .IP \(bu .B _POSIX_C_SOURCE -with the value 200809L or greater. +with the value 2008\[aq]09L or greater. .PP For the .B TRAP_*
man2/spu_run.2 +4 -4
@@ -136,7 +136,7 @@ SPU has tried to execute an invalid instruction. .B 0x40 SPU has tried to access an invalid channel. .TP -.B 0x3fff0000 +.B 0x3fff\[aq]0000 The bits masked with this value contain the code returned from a .B stop-and-signal instruction.
@@ -245,9 +245,9 @@ int main(void) err(EXIT_FAILURE, "open"); /* - * We should see a status code of 0x12340002: - * 0x00000002 (spu was stopped due to stop\-and\-signal) - * | 0x12340000 (the stop\-and\-signal code) + * We should see a status code of 0x1234\[aq]0002: + * 0x0000\[aq]0002 (spu was stopped due to stop\-and\-signal) + * | 0x1234\[aq]0000 (the stop\-and\-signal code) */ printf("SPU Status: %#08x\en", spu_status);
man2/statx.2 +1 -1
@@ -559,7 +559,7 @@ Reserved flag specified in .IR mask . (Currently, there is one such flag, designated by the constant .BR STATX__RESERVED , -with the value 0x80000000U.) +with the value 0x8000\[aq]0000U.) .TP .B ELOOP Too many symbolic links encountered while traversing the pathname.
man2/syscall.2 +1 -1
@@ -176,7 +176,7 @@ arm/EABI swi 0x0 r7 r0 r1 - arm64 svc #0 w8 x0 x1 - blackfin excpt 0x0 P0 R0 - - i386 int $0x80 eax eax edx - -ia64 break 0x100000 r15 r8 r9 r10 1, 6 +ia64 break 0x10\[aq]0000 r15 r8 r9 r10 1, 6 loongarch syscall 0 a7 a0 - - m68k trap #0 d0 d0 - - microblaze brki r14,8 r12 r3 - -
man2/timer_settime.2 +2 -2
@@ -28,7 +28,7 @@ Feature Test Macro Requirements for glibc (see .BR timer_settime (), .BR timer_gettime (): .nf - _POSIX_C_SOURCE >= 199309L + _POSIX_C_SOURCE >= 1993\[aq]09L .fi .SH DESCRIPTION .BR timer_settime ()
@@ -171,7 +171,7 @@ may fail with the following errors: .I new_value.it_value is negative; or .I new_value.it_value.tv_nsec -is negative or greater than 999,999,999. +is negative or greater than 999\[aq]999\[aq]999. .SH VERSIONS These system calls are available since Linux 2.6. .SH STANDARDS
man2/timerfd_create.2 +1 -1
@@ -461,7 +461,7 @@ See NOTES. .I new_value is not properly initialized (one of the .I tv_nsec -falls outside the range zero to 999,999,999). +falls outside the range zero to 999\[aq]999\[aq]999). .TP .B EINVAL .\" This case only checked since Linux 2.6.29, and Linux 2.2.2[78].some-stable-version.
man2/truncate.2 +2 -2
@@ -125,7 +125,7 @@ Too many symbolic links were encountered in translating the pathname. .TP .B ENAMETOOLONG A component of a pathname exceeded 255 characters, -or an entire pathname exceeded 1023 characters. +or an entire pathname exceeded 1\[aq]023 characters. .TP .B ENOENT The named file does not exist.
@@ -240,7 +240,7 @@ A header file bug in glibc 2.12 meant that the minimum value of .B _POSIX_C_SOURCE required to expose the declaration of .BR ftruncate () -was 200809L instead of 200112L. +was 2008\[aq]09L instead of 2001\[aq]12L. This has been fixed in later glibc versions. .SH SEE ALSO .BR truncate (1),
man2/utimensat.2 +3 -3
@@ -28,7 +28,7 @@ Feature Test Macro Requirements for glibc (see .BR utimensat (): .nf Since glibc 2.10: - _POSIX_C_SOURCE >= 200809L + _POSIX_C_SOURCE >= 2008\[aq]09L Before glibc 2.10: _ATFILE_SOURCE .fi
@@ -36,7 +36,7 @@ Feature Test Macro Requirements for glibc (see .BR futimens (): .nf Since glibc 2.10: - _POSIX_C_SOURCE >= 200809L + _POSIX_C_SOURCE >= 2008\[aq]09L Before glibc 2.10: _GNU_SOURCE .fi
@@ -272,7 +272,7 @@ Invalid value in .B EINVAL Invalid value in one of the .I tv_nsec -fields (value outside range [0, 999999999], and not +fields (value outside range [0, 999\[aq]999\[aq]999], and not .B UTIME_NOW or .BR UTIME_OMIT );
man2/write.2 +1 -1
@@ -268,7 +268,7 @@ the call succeeds, and returns the number of bytes written. On Linux, .BR write () (and similar system calls) will transfer at most -0x7ffff000 (2,147,479,552) bytes, +0x7fff\[aq]f000 (2\[aq]147\[aq]479\[aq]552) bytes, returning the number of bytes actually transferred. .\" commit e28cc71572da38a5a12c1cfe4d7032017adccf69 (This is true on both 32-bit and 64-bit systems.)
Hi Brian,
It seems using --inline is not what we're looking for. Could you please try with --no-attach?
Thanks,
Alex
Quoted 71 lines · Brian Inglis
man2/: use C digit separators with \\[aq] to show "'" or ISO/IEC suffixes to clarify long binary, octal, hex, decimal numeric strings; use consistent interval notation for value ranges;
fix minor discrepancies.[PATCH 01/11] man2/shmget.2: fix limit units suffix from SI to IEC
[PATCH 02/11] man2/spu_run.2: fix example comment status code or-ed value
[PATCH 03/11] man2/: use consistent interval notation for value ranges
[PATCH 04/11] man2/open.2: punctuate octal perms with digit separators
[PATCH 05/11] man2/reboot.2: show BCD dates in hex not decimal
[PATCH 06/11] man2/reboot.2: punctuate hex in docs with digit separators
[PATCH 07/11] man2/statfs.2: punctuate hex in docs with digit separators
[PATCH 08/11] man2/adjtimex.2: use ISO/IEC suffixes and digit separators in ranges and example docs [PATCH 09/11] man2/getrandom.2: change limit to use IEC suffix
[PATCH 10/11] man2/futex.2: change limit to use ISO suffix
[PATCH 11/11] man2/: punctuate long numeric strings with digit separatorsBrian Inglis (11):
man2/shmget.2: fix limit units suffix from SI to IEC
man2/spu_run.2: fix example comment status code or-ed value
man2/: use consistent interval notation for value ranges
man2/open.2: punctuate octal perms with digit separators
man2/reboot.2: show BCD dates in hex not decimal
man2/reboot.2: punctuate hex in docs with digit separators man2/statfs.2: punctuate hex in docs with digit separators man2/adjtimex.2: use ISO/IEC suffixes and digit separators in ranges and example docs man2/getrandom.2: change limit to use IEC suffix
man2/futex.2: change limit to use ISO suffix
man2/: punctuate long numeric strings with digit separatorsman2/add_key.2 | 2 +- man2/adjtimex.2 | 12 ++--- man2/clock_getres.2 | 2 +- man2/clock_nanosleep.2 | 2 +- man2/eventfd.2 | 6 +-- man2/execve.2 | 2 +- man2/fcntl.2 | 4 +- man2/futex.2 | 2 +- man2/getitimer.2 | 4 +- man2/getrandom.2 | 2 +- man2/gettimeofday.2 | 2 +- man2/ioctl.2 | 4 +- man2/ioctl_console.2 | 2 +- man2/ioctl_getfsmap.2 | 4 +- man2/ioperm.2 | 2 +- man2/kexec_load.2 | 2 +- man2/link.2 | 4 +- man2/msgget.2 | 2 +- man2/nanosleep.2 | 4 +- man2/open.2 | 32 ++++++------ man2/pciconfig_read.2 | 2 +- man2/perf_event_open.2 | 2 +- man2/personality.2 | 8 +-- man2/prctl.2 | 2 +- man2/read.2 | 2 +- man2/reboot.2 | 24 ++++----- man2/semget.2 | 4 +- man2/sendfile.2 | 2 +- man2/shmget.2 | 2 +- man2/sigaction.2 | 4 +- man2/spu_run.2 | 8 +-- man2/statfs.2 | 110 ++++++++++++++++++++--------------------- man2/statx.2 | 2 +- man2/syscall.2 | 2 +- man2/timer_settime.2 | 4 +- man2/timerfd_create.2 | 2 +- man2/truncate.2 | 4 +- man2/utimensat.2 | 6 +-- man2/write.2 | 2 +- 39 files changed, 144 insertions(+), 144 deletions(-)
Signature · 2 lines
<http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
Quoted 3 lines · Alejandro Colomar
Hi Brian,
It seems using --inline is not what we're looking for. Could you please try with --no-attach?
Ahh, no sorry. It might be enough. It seems it has it attached, but I can also see it in the email itself.
Quoted 78 lines
Thanks,
Alex
Quoted 71 lines · Brian Inglis
man2/: use C digit separators with \\[aq] to show "'" or ISO/IEC suffixes to clarify long binary, octal, hex, decimal numeric strings; use consistent interval notation for value ranges;
fix minor discrepancies.[PATCH 01/11] man2/shmget.2: fix limit units suffix from SI to IEC
[PATCH 02/11] man2/spu_run.2: fix example comment status code or-ed value
[PATCH 03/11] man2/: use consistent interval notation for value ranges
[PATCH 04/11] man2/open.2: punctuate octal perms with digit separators
[PATCH 05/11] man2/reboot.2: show BCD dates in hex not decimal
[PATCH 06/11] man2/reboot.2: punctuate hex in docs with digit separators
[PATCH 07/11] man2/statfs.2: punctuate hex in docs with digit separators
[PATCH 08/11] man2/adjtimex.2: use ISO/IEC suffixes and digit separators in ranges and example docs [PATCH 09/11] man2/getrandom.2: change limit to use IEC suffix
[PATCH 10/11] man2/futex.2: change limit to use ISO suffix
[PATCH 11/11] man2/: punctuate long numeric strings with digit separatorsBrian Inglis (11):
man2/shmget.2: fix limit units suffix from SI to IEC
man2/spu_run.2: fix example comment status code or-ed value
man2/: use consistent interval notation for value ranges
man2/open.2: punctuate octal perms with digit separators
man2/reboot.2: show BCD dates in hex not decimal
man2/reboot.2: punctuate hex in docs with digit separators man2/statfs.2: punctuate hex in docs with digit separators man2/adjtimex.2: use ISO/IEC suffixes and digit separators in ranges and example docs man2/getrandom.2: change limit to use IEC suffix
man2/futex.2: change limit to use ISO suffix
man2/: punctuate long numeric strings with digit separatorsman2/add_key.2 | 2 +- man2/adjtimex.2 | 12 ++--- man2/clock_getres.2 | 2 +- man2/clock_nanosleep.2 | 2 +- man2/eventfd.2 | 6 +-- man2/execve.2 | 2 +- man2/fcntl.2 | 4 +- man2/futex.2 | 2 +- man2/getitimer.2 | 4 +- man2/getrandom.2 | 2 +- man2/gettimeofday.2 | 2 +- man2/ioctl.2 | 4 +- man2/ioctl_console.2 | 2 +- man2/ioctl_getfsmap.2 | 4 +- man2/ioperm.2 | 2 +- man2/kexec_load.2 | 2 +- man2/link.2 | 4 +- man2/msgget.2 | 2 +- man2/nanosleep.2 | 4 +- man2/open.2 | 32 ++++++------ man2/pciconfig_read.2 | 2 +- man2/perf_event_open.2 | 2 +- man2/personality.2 | 8 +-- man2/prctl.2 | 2 +- man2/read.2 | 2 +- man2/reboot.2 | 24 ++++----- man2/semget.2 | 4 +- man2/sendfile.2 | 2 +- man2/shmget.2 | 2 +- man2/sigaction.2 | 4 +- man2/spu_run.2 | 8 +-- man2/statfs.2 | 110 ++++++++++++++++++++--------------------- man2/statx.2 | 2 +- man2/syscall.2 | 2 +- man2/timer_settime.2 | 4 +- man2/timerfd_create.2 | 2 +- man2/truncate.2 | 4 +- man2/utimensat.2 | 6 +-- man2/write.2 | 2 +- 39 files changed, 144 insertions(+), 144 deletions(-)
Signature · 2 lines
<http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
Quoted 3 lines · Alejandro Colomar
Quoted 1 line · Alejandro Colomar
It seems using --inline is not what we're looking for. Could you please try with --no-attach?
Ahh, no sorry. It might be enough. It seems it has it attached, but I can also see it in the email itself.
I see we're both using Thunderbird, and I saw no difference in the view of my copies of the patches, other than if you view Message Source, the internal MIME headers show:
Content-Disposition: {attachment|inline}; filename="v2-00??-man2-*.patch"
I note that I have TB main menu View/Display Attachments inline checked.
Signature · 6 lines
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut -- Antoine de Saint-Exupéry
Hi Brian,
Quoted 6 lines · Brian Inglis
Quoted 3 lines · Alejandro Colomar
Quoted 1 line · Alejandro Colomar
It seems using --inline is not what we're looking for. Could you please try with --no-attach?
Ahh, no sorry. It might be enough. It seems it has it attached, but I can also see it in the email itself.
I see we're both using Thunderbird,
I started using neomutt(1) yesterday, but yes, I'm still using TB until I'm more comfortable with it :)
Quoted 6 lines
and I saw no difference in the view of my
copies of the patches, other than if you view Message Source, the internal MIME headers show:
Content-Disposition: {attachment|inline}; filename="v2-00??-man2-*.patch"I note that I have TB main menu View/Display Attachments inline checked.
I do have that, but see them different :|
Cheers,
Alex
Quoted 1 line
Signature · 2 lines
<http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
Hi Brian,
Quoted 5 lines · Brian Inglis
man2/: use C digit separators with \\[aq] to show "'" or ISO/IEC suffixes to clarify long binary, octal, hex, decimal numeric strings; use consistent interval notation for value ranges;
fix minor discrepancies.
Quoted 11 lines
[PATCH 01/11] man2/shmget.2: fix limit units suffix from SI to IEC
[PATCH 02/11] man2/spu_run.2: fix example comment status code or-ed value
[PATCH 03/11] man2/: use consistent interval notation for value ranges
[PATCH 04/11] man2/open.2: punctuate octal perms with digit separators
[PATCH 05/11] man2/reboot.2: show BCD dates in hex not decimal
[PATCH 06/11] man2/reboot.2: punctuate hex in docs with digit separators
[PATCH 07/11] man2/statfs.2: punctuate hex in docs with digit separators
[PATCH 08/11] man2/adjtimex.2: use ISO/IEC suffixes and digit separators in ranges and example docs [PATCH 09/11] man2/getrandom.2: change limit to use IEC suffix
[PATCH 10/11] man2/futex.2: change limit to use ISO suffix
[PATCH 11/11] man2/: punctuate long numeric strings with digit separators
I've applied some of these patches. Please rebase the rest, fix some minor comments that I made about them (in those that I did), and send v3 when you can :)
Cheers,
Alex
Quoted 55 lines
Brian Inglis (11):
man2/shmget.2: fix limit units suffix from SI to IEC
man2/spu_run.2: fix example comment status code or-ed value
man2/: use consistent interval notation for value ranges
man2/open.2: punctuate octal perms with digit separators
man2/reboot.2: show BCD dates in hex not decimal
man2/reboot.2: punctuate hex in docs with digit separators man2/statfs.2: punctuate hex in docs with digit separators man2/adjtimex.2: use ISO/IEC suffixes and digit separators in ranges and example docs man2/getrandom.2: change limit to use IEC suffix
man2/futex.2: change limit to use ISO suffix
man2/: punctuate long numeric strings with digit separatorsman2/add_key.2 | 2 +- man2/adjtimex.2 | 12 ++--- man2/clock_getres.2 | 2 +- man2/clock_nanosleep.2 | 2 +- man2/eventfd.2 | 6 +-- man2/execve.2 | 2 +- man2/fcntl.2 | 4 +- man2/futex.2 | 2 +- man2/getitimer.2 | 4 +- man2/getrandom.2 | 2 +- man2/gettimeofday.2 | 2 +- man2/ioctl.2 | 4 +- man2/ioctl_console.2 | 2 +- man2/ioctl_getfsmap.2 | 4 +- man2/ioperm.2 | 2 +- man2/kexec_load.2 | 2 +- man2/link.2 | 4 +- man2/msgget.2 | 2 +- man2/nanosleep.2 | 4 +- man2/open.2 | 32 ++++++------ man2/pciconfig_read.2 | 2 +- man2/perf_event_open.2 | 2 +- man2/personality.2 | 8 +-- man2/prctl.2 | 2 +- man2/read.2 | 2 +- man2/reboot.2 | 24 ++++----- man2/semget.2 | 4 +- man2/sendfile.2 | 2 +- man2/shmget.2 | 2 +- man2/sigaction.2 | 4 +- man2/spu_run.2 | 8 +-- man2/statfs.2 | 110 ++++++++++++++++++++--------------------- man2/statx.2 | 2 +- man2/syscall.2 | 2 +- man2/timer_settime.2 | 4 +- man2/timerfd_create.2 | 2 +- man2/truncate.2 | 4 +- man2/utimensat.2 | 6 +-- man2/write.2 | 2 +- 39 files changed, 144 insertions(+), 144 deletions(-)
Signature · 2 lines
<http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5