From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org
Cc: ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org,
bpf@vger.kernel.org, luke.r.nels@gmail.com, xi.wang@gmail.com,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH bpf-next v2 0/4] Various RISC-V BPF improvements
Date: Mon, 01 Nov 2021 16:20:08 +0000 [thread overview]
Message-ID: <163578360870.18867.4815897974014023266.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211028161057.520552-1-bjorn@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 28 Oct 2021 18:10:53 +0200 you wrote:
> Unfortunately selftest/bpf does not build for RV64. This series fixes
> that.
>
> * JIT requires more iterations to converge
> * Some Makefile issues
> * bpf_tracing.h was missing RISC-V macros for PT_REGS
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/4] riscv, bpf: Increase the maximum number of iterations
https://git.kernel.org/bpf/bpf-next/c/4b54214f39ff
- [bpf-next,v2,2/4] tools build: Add RISC-V to HOSTARCH parsing
https://git.kernel.org/bpf/bpf-next/c/b390d69831ee
- [bpf-next,v2,3/4] riscv, libbpf: Add RISC-V (RV64) support to bpf_tracing.h
https://git.kernel.org/bpf/bpf-next/c/589fed479ba1
- [bpf-next,v2,4/4] selftests/bpf: Fix broken riscv build
https://git.kernel.org/bpf/bpf-next/c/36e70b9b06bf
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2021-11-01 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 16:10 [PATCH bpf-next v2 0/4] Various RISC-V BPF improvements Björn Töpel
2021-10-28 16:10 ` [PATCH bpf-next v2 1/4] riscv, bpf: Increase the maximum number of iterations Björn Töpel
2021-10-28 16:10 ` [PATCH bpf-next v2 2/4] tools build: Add RISC-V to HOSTARCH parsing Björn Töpel
2021-10-28 16:10 ` [PATCH bpf-next v2 3/4] riscv, libbpf: Add RISC-V (RV64) support to bpf_tracing.h Björn Töpel
2021-10-28 16:10 ` [PATCH bpf-next v2 4/4] selftests/bpf: Fix broken riscv build Björn Töpel
2021-11-01 16: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=163578360870.18867.4815897974014023266.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-riscv@lists.infradead.org \
--cc=luke.r.nels@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=xi.wang@gmail.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