From: Florian Weimer <fw@deneb.enyo.de>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lseek.2: SYNOPSIS: Use correct types
Date: Sun, 22 Nov 2020 13:43:18 +0100 [thread overview]
Message-ID: <87wnydblzt.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20201121173054.12172-1-alx.manpages@gmail.com> (Alejandro Colomar's message of "Sat, 21 Nov 2020 18:30:56 +0100")
* Alejandro Colomar:
> The Linux kernel uses 'unsigned int' instead of 'int' for 'fd' and
> 'whence'. As glibc provides no wrapper, use the same types the
> kernel uses.
lseek is a POSIX interface, and glibc provides it. POSIX uses int for
file descriptors (and the whence parameter in case of lseek).
The llseek system call is a different matter, that's indeed
Linux-specific.
next prev parent reply other threads:[~2020-11-22 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 17:30 [PATCH] lseek.2: SYNOPSIS: Use correct types Alejandro Colomar
2020-11-21 17:45 ` Alejandro Colomar (man-pages)
2020-11-22 22:37 ` Michael Kerrisk (man-pages)
2020-11-22 12:43 ` Florian Weimer [this message]
2020-11-22 13:14 ` Alejandro Colomar (man-pages)
2020-11-22 22:32 ` Michael Kerrisk (man-pages)
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=87wnydblzt.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=alx.manpages@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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