From: patchwork-bot+netdevbpf@kernel.org
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, john.fastabend@gmail.com, jolsa@kernel.org,
houtao@huaweicloud.com, song@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v7 0/2] Skip callback tests if jit is disabled in test_verifier
Date: Wed, 24 Jan 2024 04:50:25 +0000 [thread overview]
Message-ID: <170607182582.16094.17473776124345852474.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240123090351.2207-1-yangtiezhu@loongson.cn>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 23 Jan 2024 17:03:49 +0800 you wrote:
> Thanks very much for the feedbacks from Eduard, John, Jiri, Daniel,
> Hou Tao, Song Liu and Andrii.
>
> v7:
> -- Add an explicit flag F_NEEDS_JIT_ENABLED for checking,
> thanks Andrii.
>
> [...]
Here is the summary with links:
- [bpf-next,v7,1/2] selftests/bpf: Move is_jit_enabled() into testing_helpers
https://git.kernel.org/bpf/bpf-next/c/15b4f88dcc0a
- [bpf-next,v7,2/2] selftests/bpf: Skip callback tests if jit is disabled in test_verifier
https://git.kernel.org/bpf/bpf-next/c/0b50478fd877
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:[~2024-01-24 4:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 9:03 [PATCH bpf-next v7 0/2] Skip callback tests if jit is disabled in test_verifier Tiezhu Yang
2024-01-23 9:03 ` [PATCH bpf-next v7 1/2] selftests/bpf: Move is_jit_enabled() into testing_helpers Tiezhu Yang
2024-01-23 9:03 ` [PATCH bpf-next v7 2/2] selftests/bpf: Skip callback tests if jit is disabled in test_verifier Tiezhu Yang
2024-01-23 19:51 ` Andrii Nakryiko
2024-01-24 4:50 ` 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=170607182582.16094.17473776124345852474.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=houtao@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=song@kernel.org \
--cc=yangtiezhu@loongson.cn \
/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