public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
	memxor@gmail.com, john.fastabend@gmail.com, kpsingh@kernel.org,
	shuah@kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, bpf@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v11 0/7] bpf-core changes for preparation of
Date: Wed, 07 Sep 2022 18:10:16 +0000	[thread overview]
Message-ID: <166257421685.4794.15651156526607551143.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220906151303.2780789-1-benjamin.tissoires@redhat.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Tue,  6 Sep 2022 17:12:56 +0200 you wrote:
> Hi,
> 
> well, given that the HID changes haven't moved a lot in the past
> revisions and that I am cc-ing a bunch of people, I have dropped them
> while we focus on the last 2 requirements in bpf-core changes.
> 
> I'll submit a HID targeted series when we get these in tree, which
> would make things a lore more independent.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v11,1/7] selftests/bpf: regroup and declare similar kfuncs selftests in an array
    https://git.kernel.org/bpf/bpf-next/c/012ba1156e4a
  - [bpf-next,v11,2/7] bpf: split btf_check_subprog_arg_match in two
    https://git.kernel.org/bpf/bpf-next/c/95f2f26f3cac
  - [bpf-next,v11,3/7] bpf/verifier: allow all functions to read user provided context
    https://git.kernel.org/bpf/bpf-next/c/15baa55ff5b0
  - [bpf-next,v11,4/7] selftests/bpf: add test for accessing ctx from syscall program type
    https://git.kernel.org/bpf/bpf-next/c/fb66223a244f
  - [bpf-next,v11,5/7] bpf/btf: bump BTF_KFUNC_SET_MAX_CNT
    https://git.kernel.org/bpf/bpf-next/c/f9b348185f4d
  - [bpf-next,v11,6/7] bpf/verifier: allow kfunc to return an allocated mem
    https://git.kernel.org/bpf/bpf-next/c/eb1f7f71c126
  - [bpf-next,v11,7/7] selftests/bpf: Add tests for kfunc returning a memory pointer
    https://git.kernel.org/bpf/bpf-next/c/22ed8d5a4652

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-09-07 18:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06 15:12 [PATCH bpf-next v11 0/7] bpf-core changes for preparation of Benjamin Tissoires
2022-09-06 15:12 ` [PATCH bpf-next v11 1/7] selftests/bpf: regroup and declare similar kfuncs selftests in an array Benjamin Tissoires
2022-09-07 17:16   ` Kumar Kartikeya Dwivedi
2022-09-06 15:12 ` [PATCH bpf-next v11 2/7] bpf: split btf_check_subprog_arg_match in two Benjamin Tissoires
2022-09-07 17:18   ` Kumar Kartikeya Dwivedi
2022-09-06 15:12 ` [PATCH bpf-next v11 3/7] bpf/verifier: allow all functions to read user provided context Benjamin Tissoires
2022-09-06 15:13 ` [PATCH bpf-next v11 4/7] selftests/bpf: add test for accessing ctx from syscall program type Benjamin Tissoires
2022-09-07 17:45   ` Kumar Kartikeya Dwivedi
2022-09-07 18:09     ` Alexei Starovoitov
2022-09-07 18:30       ` Benjamin Tissoires
2022-09-06 15:13 ` [PATCH bpf-next v11 5/7] bpf/btf: bump BTF_KFUNC_SET_MAX_CNT Benjamin Tissoires
2022-09-07 18:05   ` Kumar Kartikeya Dwivedi
2022-09-06 15:13 ` [PATCH bpf-next v11 6/7] bpf/verifier: allow kfunc to return an allocated mem Benjamin Tissoires
2022-09-06 15:13 ` [PATCH bpf-next v11 7/7] selftests/bpf: Add tests for kfunc returning a memory pointer Benjamin Tissoires
2022-09-07 18:04   ` Kumar Kartikeya Dwivedi
2022-09-07 18:10 ` 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=166257421685.4794.15651156526607551143.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=memxor@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.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