From: sashiko-bot@kernel.org
To: "Hisam Mehboob" <hisamshar@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] tools/include/linux/types.h: add ulong typedef for musl compatibility
Date: Sun, 31 May 2026 15:01:11 +0000 [thread overview]
Message-ID: <20260531150112.5084E1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260531144934.403888-3-hisamshar@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Adding `ulong` typedef to `tools/include/linux/types.h` causes a `-Werror=redundant-decls` build failure in host tools like `perf`.
--
commit 88e8d7a9a4205d14733be0e5978d3a32589a15e0
Author: Hisam Mehboob <hisamshar@gmail.com>
tools/include/linux/types.h: add ulong typedef for musl compatibility
This commit adds a ulong typedef to tools/include/linux/types.h to fix build
failures in KVM selftests when using the musl libc.
> diff --git a/tools/include/linux/types.h b/tools/include/linux/types.h
> index d41f8a261bce8..ccc90dd4baeb2 100644
> --- a/tools/include/linux/types.h
> +++ b/tools/include/linux/types.h
> @@ -42,6 +42,7 @@ typedef __s16 s16;
> typedef __u8 u8;
> typedef __s8 s8;
>
> +typedef unsigned long ulong;
[Severity: Low]
Will this unconditional typedef cause a build failure in other host tools
like perf?
Because glibc and musl <sys/types.h> also provide a ulong typedef, adding
this here without guards triggers a -Werror=redundant-decls build failure
in tools like perf, which compile with -Wredundant-decls (via EXTRA_WARNINGS
in tools/scripts/Makefile.include) alongside -Werror.
> typedef unsigned long long ullong;
>
> #ifdef __CHECKER__
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260531144934.403888-3-hisamshar@gmail.com?part=1
next prev parent reply other threads:[~2026-05-31 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 14:49 [PATCH] tools/include/linux/types.h: add ulong typedef for musl compatibility Hisam Mehboob
2026-05-31 15:01 ` sashiko-bot [this message]
2026-06-01 20:53 ` Hisam Mehboob
2026-06-18 20:03 ` Hisam Mehboob
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=20260531150112.5084E1F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=hisamshar@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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