[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87lefpehgo.fsf@gentoo.org>
Date: Sun, 09 Jul 2023 07:16:17 +0100
From: Sam James <sam@...too.org>
To: libc-coord@...ts.openwall.com
Cc: Alejandro Colomar <alx@...nel.org>, "A . Wilcox"
<AWilcox@...cox-tech.com>, Jonathan Wakely <jwakely@...hat.com>, Rich
Felker <dalias@...c.org>, linux-man@...r.kernel.org,
libc-alpha@...rceware.org, musl@...ts.openwall.com, Sam James
<sam@...too.org>, Szabolcs Nagy <nsz@...t70.net>, Jakub Wilk
<jwilk@...lk.net>, Paul Eggert <eggert@...ucla.edu>
Subject: Re: [libc-coord] [PATCH v4] off64_t: prefer off_t for splice, etc.
Paul Eggert <eggert@...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.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
