From: patchwork-bot+netdevbpf@kernel.org
To: Tony Ambardar <tony.ambardar@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, mykolal@fb.com,
shuah@kernel.org, yatsenko@meta.com
Subject: Re: [PATCH bpf v1] selftests/bpf: Fix undefined UINT_MAX in veristat.c
Date: Thu, 16 Jan 2025 23:30:32 +0000 [thread overview]
Message-ID: <173707023227.1619724.5787640490693896648.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250116075036.3459898-1-tony.ambardar@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 15 Jan 2025 23:50:36 -0800 you wrote:
> Include <limits.h> in 'veristat.c' to provide a UINT_MAX definition and
> avoid multiple compile errors against mips64el/musl-libc:
>
> veristat.c: In function 'max_verifier_log_size':
> veristat.c:1135:36: error: 'UINT_MAX' undeclared (first use in this function)
> 1135 | const int SMALL_LOG_SIZE = UINT_MAX >> 8;
> | ^~~~~~~~
> veristat.c:24:1: note: 'UINT_MAX' is defined in header '<limits.h>'; did you forget to '#include <limits.h>'?
> 23 | #include <math.h>
> +++ |+#include <limits.h>
> 24 |
>
> [...]
Here is the summary with links:
- [bpf,v1] selftests/bpf: Fix undefined UINT_MAX in veristat.c
https://git.kernel.org/bpf/bpf-next/c/a8d1c48d0720
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-01-16 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 7:50 [PATCH bpf v1] selftests/bpf: Fix undefined UINT_MAX in veristat.c Tony Ambardar
2025-01-16 23:30 ` patchwork-bot+netdevbpf [this message]
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=173707023227.1619724.5787640490693896648.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tony.ambardar@gmail.com \
--cc=yatsenko@meta.com \
--cc=yonghong.song@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