From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
lkp@intel.com, 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
Subject: Re: [PATCH bpf-next] selftests/bpf: Add missing prototypes for several test kfuncs
Date: Thu, 08 Jun 2023 11:30:20 +0000 [thread overview]
Message-ID: <168622382089.11699.11534563556655685113.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230607224046.236510-1-jolsa@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 7 Jun 2023 15:40:46 -0700 you wrote:
> Adding missing prototypes for several kfuncs that are used by
> test_verifier tests. We don't really need kfunc prototypes for
> these tests, but adding them to silence 'make W=1' build and
> to have all test kfuncs declarations in bpf_testmod_kfunc.h.
>
> Also moving __diag_pop for -Wmissing-prototypes to cover also
> bpf_testmod_test_write and bpf_testmod_test_read and adding
> bpf_fentry_shadow_test in there as well. All of them need to
> be exported, but there's no need for declarations.
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Add missing prototypes for several test kfuncs
https://git.kernel.org/bpf/bpf-next/c/67faabbde36b
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:[~2023-06-08 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 22:40 [PATCH bpf-next] selftests/bpf: Add missing prototypes for several test kfuncs Jiri Olsa
2023-06-08 11:30 ` 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=168622382089.11699.11534563556655685113.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=lkp@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.