From: Sam James <sam@gentoo.org>
To: libc-coord@lists.openwall.com
Cc: Alejandro Colomar <alx@kernel.org>,
"A . Wilcox" <AWilcox@wilcox-tech.com>,
Jonathan Wakely <jwakely@redhat.com>,
Rich Felker <dalias@libc.org>,
linux-man@vger.kernel.org, libc-alpha@sourceware.org,
musl@lists.openwall.com, Sam James <sam@gentoo.org>,
Szabolcs Nagy <nsz@port70.net>, Jakub Wilk <jwilk@jwilk.net>,
Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: [libc-coord] [PATCH v4] off64_t: prefer off_t for splice, etc.
Date: Sun, 09 Jul 2023 07:16:17 +0100 [thread overview]
Message-ID: <87lefpehgo.fsf@gentoo.org> (raw)
In-Reply-To: <20230709061011.1885809-1-eggert@cs.ucla.edu>
Paul Eggert <eggert@cs.ucla.edu> writes:
> For the few functions that come only in 64-bit off_t flavors,
> document their APIs as using off_t instead of off64_t,
> and say also that code should #define _FILE_OFFSET_BITS 64.
> This documents what user code is (and should be) doing anyway,
> if it needs to work on traditional x86 and ARM Linux.
LGTM and thank you Paul.
I haven't checked for other prototypes/examples which need
changing.
next prev parent reply other threads:[~2023-07-09 6:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 17:53 regression in man pages for interfaces using loff_t Rich Felker
2023-06-28 18:21 ` Paul Eggert
2023-06-28 19:15 ` Rich Felker
2023-06-30 7:11 ` Paul Eggert
[not found] ` <CACb0b4nkLFOi4q=SSBSD_7aH4FRt9H4sRHQz6wF5O-x9PiwnFA@mail.gmail.com>
2023-06-30 8:14 ` [libc-coord] " Jonathan Wakely
2023-06-30 8:30 ` Sam James
2023-06-30 19:44 ` Paul Eggert
[not found] ` <9751E98E-025B-4E32-9EDF-D1984F998C10@wilcox-tech.com>
2023-07-02 19:21 ` [musl] " Paul Eggert
2023-07-03 18:16 ` Jakub Wilk
2023-07-03 21:35 ` Paul Eggert
2023-07-08 17:03 ` Alejandro Colomar
2023-07-09 6:07 ` [PATCH v4] off64_t: prefer off_t for splice, etc Paul Eggert
2023-07-09 6:16 ` Sam James [this message]
2023-07-15 15:08 ` [libc-coord] " Alejandro Colomar
2023-07-15 18:35 ` [musl] " Rich Felker
2023-07-15 20:01 ` Paul Eggert
2023-07-16 0:35 ` Alejandro Colomar
2023-07-16 0:39 ` Alejandro Colomar
2023-06-30 23:37 ` [musl] Re: regression in man pages for interfaces using loff_t Rich Felker
2023-07-01 7:24 ` [libc-coord] " Paul Eggert
2023-07-01 13:36 ` Szabolcs Nagy
2023-07-01 23:02 ` Paul Eggert
2023-07-01 14:32 ` [musl] " Rich Felker
2023-07-01 18:45 ` Alejandro Colomar
2023-07-01 23:06 ` Paul Eggert
2023-06-28 19:19 ` Szabolcs Nagy
2023-06-28 19:28 ` [musl] " Rich Felker
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=87lefpehgo.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=AWilcox@wilcox-tech.com \
--cc=alx@kernel.org \
--cc=dalias@libc.org \
--cc=eggert@cs.ucla.edu \
--cc=jwakely@redhat.com \
--cc=jwilk@jwilk.net \
--cc=libc-alpha@sourceware.org \
--cc=libc-coord@lists.openwall.com \
--cc=linux-man@vger.kernel.org \
--cc=musl@lists.openwall.com \
--cc=nsz@port70.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.