From: Arnd Bergmann <arnd@arndb.de>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: David Laight <David.Laight@aculab.com>,
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 15:34:22 +0100 [thread overview]
Message-ID: <CAK8P3a1Rvf_+qmQ5pyDeKweVOFM_GoOKnG4HA3Ffs6LeVuoDhA@mail.gmail.com> (raw)
In-Reply-To: <YaTAffbvzxGGsVIv@yuki>
On Mon, Nov 29, 2021 at 12:58 PM Cyril Hrubis <chrubis@suse.cz> wrote:
>
> What about guarding the change with __STDINT_COMPATIBLE_TYPES__ as:
>
> #if defined(__STDINT_COMPATIBLE_TYPES__)
> # include <stdint.h>
>
> typedef __u64 uint64_t;
> ...
I don't think we can include stdint.h here, the entire point of the custom
kernel types is to ensure the other kernel headers can use these types
without relying on libc headers.
While some of driver specific kernel headers have libc dependencies
in them, the general rule is to keep the kernel headers as standalone
usable.
Arnd
next prev parent reply other threads:[~2021-11-29 14:36 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 [this message]
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 ` 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=CAK8P3a1Rvf_+qmQ5pyDeKweVOFM_GoOKnG4HA3Ffs6LeVuoDhA@mail.gmail.com \
--to=arnd@arndb.de \
--cc=David.Laight@aculab.com \
--cc=chrubis@suse.cz \
--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 NNTP newsgroup(s).