public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	bpf@vger.kernel.org, kafai@fb.com, songliubraving@fb.com,
	yhs@fb.com, john.fastabend@gmail.com, kpsingh@chromium.org,
	sdf@google.com, haoluo@google.com, void@manifault.com,
	memxor@gmail.com
Subject: Re: [PATCHv4 bpf-next 00/10] bpf: Move kernel test kfuncs into bpf_testmod
Date: Wed, 17 May 2023 05:20:22 +0000	[thread overview]
Message-ID: <168430082282.27237.3835689466845721990.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230515133756.1658301-1-jolsa@kernel.org>

Hello:

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

On Mon, 15 May 2023 15:37:46 +0200 you wrote:
> hi,
> I noticed several times in discussions that we should move test kfuncs
> into kernel module, now perhaps even more pressing with all the kfunc
> effort. This patchset moves all the test kfuncs into bpf_testmod.
> 
> I added bpf_testmod/bpf_testmod_kfunc.h header that is shared between
> bpf_testmod kernel module and BPF programs.
> 
> [...]

Here is the summary with links:
  - [PATCHv4,bpf-next,01/10] libbpf: Store zero fd to fd_array for loader kfunc relocation
    https://git.kernel.org/bpf/bpf-next/c/10cb8622b695
  - [PATCHv4,bpf-next,02/10] selftests/bpf: Move kfunc exports to bpf_testmod/bpf_testmod_kfunc.h
    https://git.kernel.org/bpf/bpf-next/c/8e9af8217124
  - [PATCHv4,bpf-next,03/10] selftests/bpf: Move test_progs helpers to testing_helpers object
    https://git.kernel.org/bpf/bpf-next/c/45db310984bf
  - [PATCHv4,bpf-next,04/10] selftests/bpf: Use only stdout in un/load_bpf_testmod functions
    https://git.kernel.org/bpf/bpf-next/c/d18decca69e3
  - [PATCHv4,bpf-next,05/10] selftests/bpf: Do not unload bpf_testmod in load_bpf_testmod
    https://git.kernel.org/bpf/bpf-next/c/b58f3f0e6f3c
  - [PATCHv4,bpf-next,06/10] selftests/bpf: Use un/load_bpf_testmod functions in tests
    https://git.kernel.org/bpf/bpf-next/c/11642eb92b3b
  - [PATCHv4,bpf-next,07/10] selftests/bpf: Load bpf_testmod for verifier test
    https://git.kernel.org/bpf/bpf-next/c/b23b385fa18f
  - [PATCHv4,bpf-next,08/10] selftests/bpf: Allow to use kfunc from testmod.ko in test_verifier
    https://git.kernel.org/bpf/bpf-next/c/f26ebdd3e4e4
  - [PATCHv4,bpf-next,09/10] selftests/bpf: Remove extern from kfuncs declarations
    https://git.kernel.org/bpf/bpf-next/c/6e2b50fa818b
  - [PATCHv4,bpf-next,10/10] bpf: Move kernel test kfuncs to bpf_testmod
    https://git.kernel.org/bpf/bpf-next/c/65eb006d85a2

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



      parent reply	other threads:[~2023-05-17  5:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 13:37 [PATCHv4 bpf-next 00/10] bpf: Move kernel test kfuncs into bpf_testmod Jiri Olsa
2023-05-15 13:37 ` [PATCHv4 bpf-next 01/10] libbpf: Store zero fd to fd_array for loader kfunc relocation Jiri Olsa
2023-05-15 13:37 ` [PATCHv4 bpf-next 02/10] selftests/bpf: Move kfunc exports to bpf_testmod/bpf_testmod_kfunc.h Jiri Olsa
2023-05-15 13:37 ` [PATCHv4 bpf-next 03/10] selftests/bpf: Move test_progs helpers to testing_helpers object Jiri Olsa
2023-05-15 13:37 ` [PATCHv4 bpf-next 04/10] selftests/bpf: Use only stdout in un/load_bpf_testmod functions Jiri Olsa
2023-05-15 13:37 ` [PATCHv4 bpf-next 05/10] selftests/bpf: Do not unload bpf_testmod in load_bpf_testmod Jiri Olsa
2023-05-15 13:37 ` [PATCHv4 bpf-next 06/10] selftests/bpf: Use un/load_bpf_testmod functions in tests Jiri Olsa
2023-05-15 13:37 ` [PATCHv4 bpf-next 07/10] selftests/bpf: Load bpf_testmod for verifier test Jiri Olsa
2023-05-15 13:37 ` [PATCHv4 bpf-next 08/10] selftests/bpf: Allow to use kfunc from testmod.ko in test_verifier Jiri Olsa
2023-05-16 21:45   ` Andrii Nakryiko
2023-05-17  5:17     ` Alexei Starovoitov
2023-05-17 14:27     ` Eduard Zingerman
2023-05-17 16:51       ` Andrii Nakryiko
2023-05-15 13:37 ` [PATCHv4 bpf-next 09/10] selftests/bpf: Remove extern from kfuncs declarations Jiri Olsa
2023-05-15 13:37 ` [PATCHv4 bpf-next 10/10] bpf: Move kernel test kfuncs to bpf_testmod Jiri Olsa
2023-05-16  2:22   ` David Vernet
2023-05-17  5: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=168430082282.27237.3835689466845721990.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=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kafai@fb.com \
    --cc=kpsingh@chromium.org \
    --cc=memxor@gmail.com \
    --cc=sdf@google.com \
    --cc=songliubraving@fb.com \
    --cc=void@manifault.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