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] selftests/bpf: use simply-expanded variables for libpcap flags
Date: Fri, 23 Aug 2024 22:30:29 +0000 [thread overview]
Message-ID: <172445222952.3101306.18132185601555679046.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240823194409.774815-1-eddyz87@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Fri, 23 Aug 2024 12:44:09 -0700 you wrote:
> Save pkg-config output for libpcap as simply-expanded variables.
> For an obscure reason 'shell' call in LDLIBS/CFLAGS recursively
> expanded variables makes *.test.o files compilation non-parallel
> when make is executed with -j option.
>
> While at it, reuse 'pkg-config --cflags' call to define
> -DTRAFFIC_MONITOR=1 option, it's exit status is the same as for
> 'pkg-config --exists'.
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: use simply-expanded variables for libpcap flags
https://git.kernel.org/bpf/bpf-next/c/5772c3458bb8
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:[~2024-08-23 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 19:44 [PATCH bpf-next] selftests/bpf: use simply-expanded variables for libpcap flags Eduard Zingerman
2024-08-23 19:49 ` Eduard Zingerman
2024-08-23 22: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=172445222952.3101306.18132185601555679046.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox