Hi Michael,
Okay, after a few days of thinking, I'm not sure about what to do in
some cases.
But I think we agree to use syscall(SYS_ ...) for syscalls with no
wrapper (such as membarrier(2)).
Is that right?
I think it may be better to separate this into 2 sets of changes.
1) Document s
Hi Michael,
On 2/19/21 1:39 PM, Michael Kerrisk (man-pages) wrote:
Hey Alex,
On 2/18/21 4:13 PM, Alejandro Colomar wrote:
Until now, the manual pages have (usually) documented only either
the glibc (or another library) wrapper for a syscall, or the
kernel syscall (this only when there's not a
Hey Alex,
On 2/18/21 4:13 PM, Alejandro Colomar wrote:
> Until now, the manual pages have (usually) documented only either
> the glibc (or another library) wrapper for a syscall, or the
> kernel syscall (this only when there's not a wrapper).
>
> Let's document both prototypes, which many times a
Until now, the manual pages have (usually) documented only either
the glibc (or another library) wrapper for a syscall, or the
kernel syscall (this only when there's not a wrapper).
Let's document both prototypes, which many times are slightly
different. This will solve a problem where documentin
4 matches
Mail list logo
