From: patchwork-bot+netdevbpf@kernel.org
To: Jose E. Marchesi <jose.marchesi@oracle.com>
Cc: bpf@vger.kernel.org, david.faust@oracle.com,
cupertino.miranda@oracle.com, andrii.nakryiko@gmail.com
Subject: Re: [PATCH bpf-next] bpf: missing trailing slash in tools/testing/selftests/bpf/Makefile
Date: Thu, 02 May 2024 16:40:30 +0000 [thread overview]
Message-ID: <171466803027.13356.14271626948887936984.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240502140831.23915-1-jose.marchesi@oracle.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 2 May 2024 16:08:31 +0200 you wrote:
> tools/lib/bpf/Makefile assumes that the patch in OUTPUT is a directory
> and that it includes a trailing slash. This seems to be a common
> expectation for OUTPUT among all the Makefiles.
>
> In the rule for runqslower in tools/testing/selftests/bpf/Makefile the
> variable BPFTOOL_OUTPUT is set to a directory name that lacks a
> trailing slash. This results in a malformed BPF_HELPER_DEFS being
> defined in lib/bpf/Makefile.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: missing trailing slash in tools/testing/selftests/bpf/Makefile
https://git.kernel.org/bpf/bpf-next/c/08e90da6872a
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-05-02 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 14:08 [PATCH bpf-next] bpf: missing trailing slash in tools/testing/selftests/bpf/Makefile Jose E. Marchesi
2024-05-02 16:40 ` 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=171466803027.13356.14271626948887936984.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=cupertino.miranda@oracle.com \
--cc=david.faust@oracle.com \
--cc=jose.marchesi@oracle.com \
/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