From: patchwork-bot+netdevbpf@kernel.org
To: Ian Rogers <irogers@google.com>
Cc: ast@kernel.org, daniel@iogearbox.net, kafai@fb.com,
songliubraving@fb.com, yhs@fb.com, andriin@fb.com,
john.fastabend@gmail.com, kpsingh@chromium.org,
quentin@isovalent.com, jean-philippe@linaro.org,
tklauser@distanz.ch, iii@linux.ibm.com, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] bpf, libbpf: Avoid unused function warning on bpf_tail_call_static
Date: Thu, 14 Jan 2021 03:20:08 +0000 [thread overview]
Message-ID: <161059440831.32332.1122850052450236500.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210113223609.3358812-1-irogers@google.com>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Wed, 13 Jan 2021 14:36:08 -0800 you wrote:
> Add inline to __always_inline making it match the linux/compiler.h.
> Adding this avoids an unused function warning on bpf_tail_call_static
> when compining with -Wall.
>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/lib/bpf/bpf_helpers.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- [1/2] bpf, libbpf: Avoid unused function warning on bpf_tail_call_static
https://git.kernel.org/bpf/bpf-next/c/ce5a518e9de5
- [2/2] tools/bpftool: Add -Wall when building BPF programs
https://git.kernel.org/bpf/bpf-next/c/bade5c554f1a
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:[~2021-01-14 3:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 22:36 [PATCH 1/2] bpf, libbpf: Avoid unused function warning on bpf_tail_call_static Ian Rogers
2021-01-13 22:36 ` [PATCH 2/2] tools/bpftool: Add -Wall when building BPF programs Ian Rogers
2021-01-14 0:49 ` Yonghong Song
2021-01-14 0:49 ` [PATCH 1/2] bpf, libbpf: Avoid unused function warning on bpf_tail_call_static Yonghong Song
2021-01-14 3: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=161059440831.32332.1122850052450236500.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=iii@linux.ibm.com \
--cc=irogers@google.com \
--cc=jean-philippe@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=songliubraving@fb.com \
--cc=tklauser@distanz.ch \
--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;
as well as URLs for NNTP newsgroup(s).