From: patchwork-bot+netdevbpf@kernel.org
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
tsbogend@alpha.franken.de, johan.almbladh@anyfinetworks.com,
paulburton@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v2 0/2] MIPS: Implement two workarounds for BPF JIT
Date: Tue, 28 Feb 2023 14:00:18 +0000 [thread overview]
Message-ID: <167759281805.14618.4922384489244430083.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230228113305.83751-1-jiaxun.yang@flygoat.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 28 Feb 2023 11:33:03 +0000 you wrote:
> Hi all,
>
> Just noticed eBPF JIT is not working on R4000 when messing around with QEMU.
>
> This patchset implements two workarounds that is blocking us from enabling eBPF
> JIT on R4000.
>
> [...]
Here is the summary with links:
- [v2,1/2] MIPS: ebpf jit: Implement DADDI workarounds
https://git.kernel.org/bpf/bpf-next/c/bbefef2f0708
- [v2,2/2] MIPS: ebpf jit: Implement R4000 workarounds
https://git.kernel.org/bpf/bpf-next/c/7364d60c2661
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:[~2023-02-28 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 11:33 [PATCH v2 0/2] MIPS: Implement two workarounds for BPF JIT Jiaxun Yang
2023-02-28 11:33 ` [PATCH v2 1/2] MIPS: ebpf jit: Implement DADDI workarounds Jiaxun Yang
2023-02-28 12:02 ` Philippe Mathieu-Daudé
2023-02-28 12:35 ` Johan Almbladh
2023-02-28 11:33 ` [PATCH v2 2/2] MIPS: ebpf jit: Implement R4000 workarounds Jiaxun Yang
2023-02-28 14: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=167759281805.14618.4922384489244430083.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=johan.almbladh@anyfinetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).