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, tongtiangen@huawei.com,
luke.r.nels@gmail.com, xi.wang@gmail.com,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH bpf-next] riscv, bpf: Fix RV32 broken build, and silence RV64 warning
Date: Fri, 05 Nov 2021 16:00:07 +0000 [thread overview]
Message-ID: <163612800715.13450.14251964534648869709.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211103115453.397209-1-bjorn@kernel.org>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 3 Nov 2021 12:54:53 +0100 you wrote:
> Commit 252c765bd764 ("riscv, bpf: Add BPF exception tables") only
> addressed RV64, and broke the RV32 build [1]. Fix by gating the exception
> tables code with CONFIG_ARCH_RV64I.
>
> Further, silence a "-Wmissing-prototypes" warning [2] in the RV64 BPF
> JIT.
>
> [...]
Here is the summary with links:
- [bpf-next] riscv, bpf: Fix RV32 broken build, and silence RV64 warning
https://git.kernel.org/bpf/bpf/c/f47d4ffe3a84
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-11-05 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 11:54 [PATCH bpf-next] riscv, bpf: Fix RV32 broken build, and silence RV64 warning Björn Töpel
2021-11-03 13:15 ` Daniel Borkmann
2021-11-03 13:29 ` tongtiangen
2021-11-03 13:35 ` Björn Töpel
2021-11-05 15:59 ` Daniel Borkmann
2021-11-05 16:00 ` 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=163612800715.13450.14251964534648869709.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=tongtiangen@huawei.com \
--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;
as well as URLs for NNTP newsgroup(s).