From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next v1] selftests/bpf: include limits.h needed for PATH_MAX directly
Date: Wed, 18 Jun 2025 14:00:29 +0000 [thread overview]
Message-ID: <175025522925.120902.1276202444786474477.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250618093134.3078870-1-eddyz87@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 18 Jun 2025 02:31:34 -0700 you wrote:
> Constant PATH_MAX is used in function unpriv_helpers.c:open_config().
> This constant is provided by include file <limits.h>.
> The dependency was added by commit [1], which does not include
> <limits.h> directly, relying instead on <limits.h> being included from
> zlib.h -> zconf.h.
> As it turns out, this is not the case for all systems, e.g. on
> Fedora 41 zlib 1.3.1 is used, and there <limits.h> is not included
> from zconf.h. Hence, there is a compilation error on Fedora 41.
>
> [...]
Here is the summary with links:
- [bpf-next,v1] selftests/bpf: include limits.h needed for PATH_MAX directly
https://git.kernel.org/bpf/bpf-next/c/cd7312a78f36
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-06-18 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 9:31 [PATCH bpf-next v1] selftests/bpf: include limits.h needed for PATH_MAX directly Eduard Zingerman
2025-06-18 12:56 ` Viktor Malik
2025-06-18 14:00 ` 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=175025522925.120902.1276202444786474477.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=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.