From: patchwork-bot+netdevbpf@kernel.org
To: Alan Maguire <alan.maguire@oracle.com>
Cc: martin.lau@linux.dev, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, bpf@vger.kernel.org, mtodorovac69@gmail.com
Subject: Re: [PATCH bpf-next] bpf: eliminate remaining "make W=1" warnings in kernel/bpf/btf.o
Date: Fri, 12 Jul 2024 15:10:32 +0000 [thread overview]
Message-ID: <172079703252.7928.12025847333447557623.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240712092859.1390960-1-alan.maguire@oracle.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Fri, 12 Jul 2024 10:28:59 +0100 you wrote:
> As reported by Mirsad [1] we still see format warnings in kernel/bpf/btf.o
> at W=1 warning level:
>
> CC kernel/bpf/btf.o
> ./kernel/bpf/btf.c: In function ‘btf_type_seq_show_flags’:
> ./kernel/bpf/btf.c:7553:21: warning: assignment left-hand side might be a candidate for a format attribute [-Wsuggest-attribute=format]
> 7553 | sseq.showfn = btf_seq_show;
> | ^
> ./kernel/bpf/btf.c: In function ‘btf_type_snprintf_show’:
> ./kernel/bpf/btf.c:7604:31: warning: assignment left-hand side might be a candidate for a format attribute [-Wsuggest-attribute=format]
> 7604 | ssnprintf.show.showfn = btf_snprintf_show;
> | ^
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: eliminate remaining "make W=1" warnings in kernel/bpf/btf.o
https://git.kernel.org/bpf/bpf-next/c/2454075f8e29
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:[~2024-07-12 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 9:28 [PATCH bpf-next] bpf: eliminate remaining "make W=1" warnings in kernel/bpf/btf.o Alan Maguire
2024-07-12 15:10 ` 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=172079703252.7928.12025847333447557623.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=mtodorovac69@gmail.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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