From: patchwork-bot+netdevbpf@kernel.org
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: andrii@kernel.org, mykolal@fb.com, ast@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
jolsa@kernel.org, shuah@kernel.org, terrelln@fb.com,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v5 0/3] selftests/bpf: Use pkg-config to determine ld flags
Date: Wed, 29 Nov 2023 06:20:25 +0000 [thread overview]
Message-ID: <170123882577.32761.1092609140496107416.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231125084253.85025-1-akihiko.odaki@daynix.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Sat, 25 Nov 2023 17:42:49 +0900 you wrote:
> When linking statically, libraries may require other dependencies to be
> included to ld flags. In particular, libelf may require libzstd. Use
> pkg-config to determine such dependencies.
>
> V4 -> V5: Introduced variables LIBELF_CFLAGS and LIBELF_LIBS.
> (Daniel Borkmann)
> Added patch "selftests/bpf: Choose pkg-config for the target".
> V3 -> V4: Added "2> /dev/null".
> V2 -> V3: Added missing "echo".
> V1 -> V2: Implemented fallback, referring to HOSTPKG_CONFIG.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/3] selftests/bpf: Choose pkg-config for the target
https://git.kernel.org/bpf/bpf-next/c/2ce344b68916
- [bpf-next,v5,2/3] selftests/bpf: Override PKG_CONFIG for static builds
https://git.kernel.org/bpf/bpf-next/c/18f6f9de98d1
- [bpf-next,v5,3/3] selftests/bpf: Use pkg-config for libelf
https://git.kernel.org/bpf/bpf-next/c/8998a479fd96
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:[~2023-11-29 6:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 8:42 [PATCH bpf-next v5 0/3] selftests/bpf: Use pkg-config to determine ld flags Akihiko Odaki
2023-11-25 8:42 ` [PATCH bpf-next v5 1/3] selftests/bpf: Choose pkg-config for the target Akihiko Odaki
2023-11-25 8:42 ` [PATCH bpf-next v5 2/3] selftests/bpf: Override PKG_CONFIG for static builds Akihiko Odaki
2023-11-25 8:42 ` [PATCH bpf-next v5 3/3] selftests/bpf: Use pkg-config for libelf Akihiko Odaki
2023-11-29 6:20 ` 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=170123882577.32761.1092609140496107416.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akihiko.odaki@daynix.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=terrelln@fb.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