From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@kernel.org
Subject: Re: [PATCH bpf-next v1 0/2] Follow ups for bpf-list set
Date: Fri, 18 Nov 2022 20:20:15 +0000 [thread overview]
Message-ID: <166880281589.7537.6028248915916238724.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221118185938.2139616-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 19 Nov 2022 00:29:36 +0530 you wrote:
> Make a few changes
> - Remove bpf_global_ma_set check at runtime, disallow calling bpf_obj_new during verification
> - Disable spin lock failure test when JIT does not support kfunc (s390x)
>
> Kumar Kartikeya Dwivedi (2):
> bpf: Disallow calling bpf_obj_new_impl on bpf_mem_alloc_init failure
> selftests/bpf: Skip spin lock failure test on s390x
>
> [...]
Here is the summary with links:
- [bpf-next,v1,1/2] bpf: Disallow calling bpf_obj_new_impl on bpf_mem_alloc_init failure
(no matching commit)
- [bpf-next,v1,2/2] selftests/bpf: Skip spin lock failure test on s390x
https://git.kernel.org/bpf/bpf-next/c/97c11d6e3154
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-11-18 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 18:59 [PATCH bpf-next v1 0/2] Follow ups for bpf-list set Kumar Kartikeya Dwivedi
2022-11-18 18:59 ` [PATCH bpf-next v1 1/2] bpf: Disallow calling bpf_obj_new_impl on bpf_mem_alloc_init failure Kumar Kartikeya Dwivedi
2022-11-18 20:17 ` Alexei Starovoitov
2022-11-20 20:46 ` Kumar Kartikeya Dwivedi
2022-11-20 22:29 ` Alexei Starovoitov
2022-11-18 18:59 ` [PATCH bpf-next v1 2/2] selftests/bpf: Skip spin lock failure test on s390x Kumar Kartikeya Dwivedi
2022-11-18 20: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=166880281589.7537.6028248915916238724.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=martin.lau@kernel.org \
--cc=memxor@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