netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org
Cc: ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org,
	bpf@vger.kernel.org, lkp@intel.com
Subject: Re: [PATCH bpf] bpf, x86: Fix "no previous prototype" warning
Date: Wed, 17 Nov 2021 14:50:09 +0000	[thread overview]
Message-ID: <163716060931.12308.3728121323940964364.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211117125708.769168-1-bjorn@kernel.org>

Hello:

This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Wed, 17 Nov 2021 13:57:08 +0100 you wrote:
> The arch_prepare_bpf_dispatcher function does not have a prototype,
> and yields the following warning when W=1 is enabled for the kernel
> build.
> 
>   >> arch/x86/net/bpf_jit_comp.c:2188:5: warning: no previous \
>   prototype for 'arch_prepare_bpf_dispatcher' [-Wmissing-prototypes]
>         2188 | int arch_prepare_bpf_dispatcher(void *image, s64 *funcs, \
> 	int num_funcs)
>              |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> [...]

Here is the summary with links:
  - [bpf] bpf, x86: Fix "no previous prototype" warning
    https://git.kernel.org/bpf/bpf/c/f45b2974cc0a

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



      reply	other threads:[~2021-11-17 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 12:57 [PATCH bpf] bpf, x86: Fix "no previous prototype" warning Björn Töpel
2021-11-17 14:50 ` 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=163716060931.12308.3728121323940964364.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).