From: Cyril Hrubis <chrubis@suse.cz>
To: David Laight <David.Laight@ACULAB.COM>
Cc: 'David Howells' <dhowells@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"ltp@lists.linux.it" <ltp@lists.linux.it>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>
Subject: Re: [PATCH] uapi: Make __{u,s}64 match {u,}int64_t in userspace
Date: Mon, 29 Nov 2021 12:58:53 +0100 [thread overview]
Message-ID: <YaTAffbvzxGGsVIv@yuki> (raw)
In-Reply-To: <ff8fc4470c8f45678e546cafe9980eff@AcuMS.aculab.com>
Hi!
> > > This changes the __u64 and __s64 in userspace on 64bit platforms from
> > > long long (unsigned) int to just long (unsigned) int in order to match
> > > the uint64_t and int64_t size in userspace.
>
> That is a massive UAPI change you can't do.
Understood.
However it can still be changed if user asks for it explicitly right?
What about guarding the change with __STDINT_COMPATIBLE_TYPES__ as:
#if defined(__STDINT_COMPATIBLE_TYPES__)
# include <stdint.h>
typedef __u64 uint64_t;
...
#else
# include <asm-generic/int-ll64.h>
#endif
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2021-11-29 11:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 16:43 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 [this message]
2021-11-29 14:34 ` Arnd Bergmann
2021-12-02 14:55 ` Zack Weinberg
2021-12-02 15:01 ` David Howells
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 ` Ping: [PATCH] uapi: Make __{u, s}64 match {u, }int64_t " 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=YaTAffbvzxGGsVIv@yuki \
--to=chrubis@suse.cz \
--cc=David.Laight@ACULAB.COM \
--cc=arnd@arndb.de \
--cc=dhowells@redhat.com \
--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 \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).