From: David Howells <dhowells@redhat.com>
To: "Zack Weinberg" <zack@owlfolio.org>
Cc: dhowells@redhat.com, "Arnd Bergmann" <arnd@arndb.de>,
"Cyril Hrubis" <chrubis@suse.cz>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
libc-alpha@sourceware.org,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"David Laight" <David.Laight@aculab.com>,
"ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [PATCH] uapi: Make __{u,s}64 match {u,}int64_t in userspace
Date: Thu, 02 Dec 2021 15:01:53 +0000 [thread overview]
Message-ID: <913509.1638457313@warthog.procyon.org.uk> (raw)
In-Reply-To: <b8d6f890-e5aa-44bf-8a55-5998efa05967@www.fastmail.com>
Zack Weinberg <zack@owlfolio.org> wrote:
> I could be persuaded otherwise with an example of a program for which
> changing __s64 from 'long long' to 'long' would break *binary* backward
> compatibility, or similarly for __u64.
C++ could break.
David
next prev parent reply other threads:[~2021-12-02 15:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 16:43 [PATCH] uapi: Make __{u,s}64 match {u,}int64_t in userspace Cyril Hrubis
2021-11-22 16:51 ` Alejandro Colomar (mailing lists)
2021-11-22 20:48 ` Arnd Bergmann
2021-11-23 9:14 ` Cyril Hrubis
2021-11-23 14:18 ` Arnd Bergmann
2021-11-23 19:50 ` Florian Weimer
2021-11-24 10:17 ` Alejandro Colomar (man-pages)
2021-11-22 22:19 ` Zack Weinberg
2021-11-23 9:15 ` Cyril Hrubis
2021-12-02 15:34 ` Rich Felker
2021-12-02 23:29 ` Rich Felker
2021-12-02 23:43 ` Adhemerval Zanella
2021-12-03 0:10 ` Zack Weinberg
2021-12-03 12:32 ` Adhemerval Zanella
2021-12-03 12:54 ` Alejandro Colomar (man-pages)
2021-11-23 16:47 ` David Howells
2021-11-23 16:58 ` David Laight
2021-11-29 11:58 ` Cyril Hrubis
2021-11-29 14:34 ` Arnd Bergmann
2021-12-02 14:55 ` Zack Weinberg
2021-12-02 15:01 ` David Howells [this message]
2021-12-02 20:48 ` Zack Weinberg
2021-12-08 15:33 ` Cyril Hrubis
2022-06-17 12:13 ` Ping: " Alejandro Colomar
2022-06-17 15:04 ` Cyril Hrubis
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=913509.1638457313@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=David.Laight@aculab.com \
--cc=arnd@arndb.de \
--cc=chrubis@suse.cz \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=zack@owlfolio.org \
/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;
as well as URLs for NNTP newsgroup(s).