From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: andrii@kernel.org, eddyz87@gmail.com, mykolal@fb.com,
bpf@vger.kernel.org, netdev@vger.kernel.org, bjorn@rivosinc.com,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, charlie@rivosinc.com
Subject: Re: [PATCH bpf-next 1/2] libbpf: Add missing per-arch include path
Date: Tue, 08 Oct 2024 03:30:33 +0000 [thread overview]
Message-ID: <172835823300.66789.3704854116445399222.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240927131355.350918-1-bjorn@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Fri, 27 Sep 2024 15:13:52 +0200 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
>
> libbpf does not include the per-arch tools include path, e.g.
> tools/arch/riscv/include. Some architectures depend those files to
> build properly.
>
> Include tools/arch/$(SUBARCH)/include in the libbpf build.
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] libbpf: Add missing per-arch include path
https://git.kernel.org/bpf/bpf-next/c/710fbca820c7
- [bpf-next,2/2] selftests: bpf: Add missing per-arch include path
https://git.kernel.org/bpf/bpf-next/c/19090f0306f1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-10-08 3:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 13:13 [PATCH bpf-next 1/2] libbpf: Add missing per-arch include path Björn Töpel
2024-09-27 13:13 ` [PATCH bpf-next 2/2] selftests: bpf: " Björn Töpel
2024-09-27 20:52 ` Andrii Nakryiko
2024-09-28 9:14 ` Björn Töpel
2024-09-27 20:50 ` [PATCH bpf-next 1/2] libbpf: " Andrii Nakryiko
2024-09-28 9:11 ` Björn Töpel
2024-10-08 3:30 ` patchwork-bot+netdevbpf [this message]
2024-11-04 10:25 ` Björn Töpel
2024-11-06 22:04 ` Andrii Nakryiko
2024-11-07 14:32 ` Björn Töpel
2024-11-04 10:04 ` Alexandre Ghiti
2024-11-05 11:46 ` Kexy Biscuit
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=172835823300.66789.3704854116445399222.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=andrii@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=bpf@vger.kernel.org \
--cc=charlie@rivosinc.com \
--cc=eddyz87@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.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).