From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@fb.com,
daniel@iogearbox.net, kernel-team@fb.com, acme@redhat.com,
rdunlap@infradead.org
Subject: Re: [PATCH bpf-next] libbpf: stop using feature-detection Makefiles
Date: Thu, 04 Feb 2021 00:30:09 +0000 [thread overview]
Message-ID: <161239860972.19398.7384749864414744822.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210203203445.3356114-1-andrii@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Wed, 3 Feb 2021 12:34:45 -0800 you wrote:
> Libbpf's Makefile relies on Linux tools infrastructure's feature detection
> framework, but libbpf's needs are very modest: it detects the presence of
> libelf and libz, both of which are mandatory. So it doesn't benefit much from
> the framework, but pays significant costs in terms of maintainability and
> debugging experience, when something goes wrong. The other feature detector,
> testing for the presernce of minimal BPF API in system headers is long
> obsolete as well, providing no value.
>
> [...]
Here is the summary with links:
- [bpf-next] libbpf: stop using feature-detection Makefiles
https://git.kernel.org/bpf/bpf-next/c/5f10c1aac8b2
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:[~2021-02-04 0:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 20:34 [PATCH bpf-next] libbpf: stop using feature-detection Makefiles Andrii Nakryiko
2021-02-03 21:31 ` John Fastabend
2021-02-03 23:29 ` Randy Dunlap
2021-02-04 0: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=161239860972.19398.7384749864414744822.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acme@redhat.com \
--cc=andrii@kernel.org \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).