All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Dave Marchevsky <davemarchevsky@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, martin.lau@kernel.org, kernel-team@fb.com,
	laoar.shao@gmail.com, olsajiri@gmail.com
Subject: Re: [PATCH v2 bpf-next 1/2] bpf: Add __bpf_kfunc_{start,end}_defs macros
Date: Thu, 02 Nov 2023 06:00:24 +0000	[thread overview]
Message-ID: <169890482499.9002.3938790944237757134.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231031215625.2343848-1-davemarchevsky@fb.com>

Hello:

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

On Tue, 31 Oct 2023 14:56:24 -0700 you wrote:
> BPF kfuncs are meant to be called from BPF programs. Accordingly, most
> kfuncs are not called from anywhere in the kernel, which the
> -Wmissing-prototypes warning is unhappy about. We've peppered
> __diag_ignore_all("-Wmissing-prototypes", ... everywhere kfuncs are
> defined in the codebase to suppress this warning.
> 
> This patch adds two macros meant to bound one or many kfunc definitions.
> All existing kfunc definitions which use these __diag calls to suppress
> -Wmissing-prototypes are migrated to use the newly-introduced macros.
> A new __diag_ignore_all - for "-Wmissing-declarations" - is added to the
> __bpf_kfunc_start_defs macro based on feedback from Andrii on an earlier
> version of this patch [0] and another recent mailing list thread [1].
> 
> [...]

Here is the summary with links:
  - [v2,bpf-next,1/2] bpf: Add __bpf_kfunc_{start,end}_defs macros
    https://git.kernel.org/bpf/bpf/c/391145ba2acc
  - [v2,bpf-next,2/2] bpf: Add __bpf_hook_{start,end} macros
    https://git.kernel.org/bpf/bpf/c/15fb6f2b6c4c

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-11-02  6:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 21:56 [PATCH v2 bpf-next 1/2] bpf: Add __bpf_kfunc_{start,end}_defs macros Dave Marchevsky
2023-10-31 21:56 ` [PATCH v2 bpf-next 2/2] bpf: Add __bpf_hook_{start,end} macros Dave Marchevsky
2023-10-31 23:03   ` Jiri Olsa
2023-11-01  2:17     ` Yafang Shao
2023-10-31 23:03 ` [PATCH v2 bpf-next 1/2] bpf: Add __bpf_kfunc_{start,end}_defs macros Jiri Olsa
2023-11-01  1:39 ` David Vernet
2023-11-01  2:19 ` Yafang Shao
2023-11-02  6:00 ` 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=169890482499.9002.3938790944237757134.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=davemarchevsky@fb.com \
    --cc=kernel-team@fb.com \
    --cc=laoar.shao@gmail.com \
    --cc=martin.lau@kernel.org \
    --cc=olsajiri@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 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.