Re: [PATCH] virtio: uapi: avoid usage of libc types

From: Michael S. Tsirkin

Date: Mon Dec 22 2025 - 05:28:37 EST


On Mon, Dec 22, 2025 at 11:22:16AM +0100, Thomas Weißschuh wrote:
> On Mon, Dec 22, 2025 at 03:39:12AM -0500, Michael S. Tsirkin wrote:
> > On Mon, Dec 22, 2025 at 09:00:33AM +0100, 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.
> > >
> > > On Linux 'unsigned long' works as a replacement for 'uintptr_t' and does
> > > not depend on libc.
> > >
> > > Signed-off-by: Thomas Weißschuh <thomas.weissschuh@xxxxxxxxxxxxx>
> >
> >
> > are you fixing other uses of uintptr_t ?
>
> I am focussing on UAPI headers which include libc headers.
> virtio_ring.h seems to be the only such header which uses uintptr_t.
> There are a few other UAPI headers which reference uintptr_t, but only
> in comments or macros.
>
> uintptr_t in regular kernel code is out of scope for me.
> While it is iffy, it doesn't actually hurt.
>
>
> Thomas

And other uses of stdint.h?