From: patchwork-bot+netdevbpf@kernel•org
To: Tiezhu Yang <yangtiezhu@loongson•cn>
Cc: ast@kernel•org, daniel@iogearbox•net, andrii@kernel•org,
kafai@fb•com, songliubraving@fb•com, yhs@fb•com,
john.fastabend@gmail•com, kpsingh@kernel•org,
lixuefeng@loongson•cn, netdev@vger•kernel.org,
bpf@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH bpf-next v3 0/2] Modify BPF_JIT_ALWAYS_ON and BPF_JIT_DEFAULT_ON
Date: Mon, 28 Feb 2022 23:40:09 +0000 [thread overview]
Message-ID: <164609160961.29256.14375573252999533886.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1645523826-18149-1-git-send-email-yangtiezhu@loongson.cn>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox•net>:
On Tue, 22 Feb 2022 17:57:04 +0800 you wrote:
> v3:
> -- Use "return failure" instead of "return in failure".
> -- Use "Enable BPF JIT by default" for config BPF_JIT_DEFAULT_ON.
>
> v2:
> -- Use the full path /proc/sys/net/core/bpf_jit_enable in the help text.
> -- Update the commit message to make it clear in patch #2.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] bpf: Add some description about BPF_JIT_ALWAYS_ON in Kconfig
https://git.kernel.org/bpf/bpf-next/c/b664e255ba3c
- [bpf-next,v3,2/2] bpf: Make BPF_JIT_DEFAULT_ON selectable in Kconfig
(no matching commit)
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:[~2022-02-28 23:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 9:57 [PATCH bpf-next v3 0/2] Modify BPF_JIT_ALWAYS_ON and BPF_JIT_DEFAULT_ON Tiezhu Yang
2022-02-22 9:57 ` [PATCH bpf-next v3 1/2] bpf: Add some description about BPF_JIT_ALWAYS_ON in Kconfig Tiezhu Yang
2022-02-22 9:57 ` [PATCH bpf-next v3 2/2] bpf: Make BPF_JIT_DEFAULT_ON selectable " Tiezhu Yang
2022-02-23 5:26 ` Song Liu
2022-02-28 23:53 ` Daniel Borkmann
2022-03-09 4:21 ` Tiezhu Yang
2022-02-28 23: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=164609160961.29256.14375573252999533886.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrii@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=john.fastabend@gmail$(echo .)com \
--cc=kafai@fb$(echo .)com \
--cc=kpsingh@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=lixuefeng@loongson$(echo .)cn \
--cc=netdev@vger$(echo .)kernel.org \
--cc=songliubraving@fb$(echo .)com \
--cc=yangtiezhu@loongson$(echo .)cn \
--cc=yhs@fb$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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