From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Miklos Szeredi" <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] fuse: uapi: use UAPI types
Date: Tue, 30 Dec 2025 22:09:23 +0100 [thread overview]
Message-ID: <26513f47-37d8-47d0-a6d2-acaa1bf8ec44@app.fastmail.com> (raw)
In-Reply-To: <20251230-uapi-fuse-v2-1-5a8788d62525@linutronix.de>
On Tue, Dec 30, 2025, at 13:10, Thomas Weißschuh wrote:
> Using libc types and headers from the UAPI headers is problematic as it
> introduces a dependency on a full C toolchain.
>
> Use the fixed-width integer types provided by the UAPI headers instead.
> To keep compatibility with non-Linux platforms, add a stdint.h fallback.
>
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2025-12-30 21:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 12:10 Thomas Weißschuh
2025-12-30 21:09 ` Arnd Bergmann [this message]
2026-01-02 22:27 ` Bernd Schubert
2026-01-03 12:44 ` Bernd Schubert
2026-01-05 8:40 ` Thomas Weißschuh
2026-01-05 8:50 ` Bernd Schubert
2026-01-05 9:57 ` Thomas Weißschuh
2026-01-05 12:09 ` Arnd Bergmann
2026-01-08 22:12 ` Bernd Schubert
2026-01-09 8:11 ` Thomas Weißschuh
2026-01-09 10:38 ` David Laight
2026-01-09 10:45 ` Bernd Schubert
2026-01-09 10:55 ` Thomas Weißschuh
2026-01-09 11:36 ` Bernd Schubert
2026-01-09 13:11 ` David Laight
2026-01-09 13:46 ` Bernd Schubert
2026-01-09 19:13 ` David Laight
2026-01-08 22:14 ` Bernd Schubert
2026-01-03 14:10 ` David Laight
2026-01-03 16:47 ` Bernd Schubert
2026-01-05 12:45 ` Miklos Szeredi
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=26513f47-37d8-47d0-a6d2-acaa1bf8ec44@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=thomas.weissschuh@linutronix.de \
/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
all inboxes | Powered by JetHome®