From: patchwork-bot+bpf@kernel.org
To: Stanislav Fomichev <sdf@google.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: properly initialize linfo in sockmap_basic
Date: Fri, 02 Oct 2020 14:50:02 +0000 [thread overview]
Message-ID: <160165020267.24758.16856928754495909228.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201002000451.1794044-1-sdf@google.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Thu, 1 Oct 2020 17:04:51 -0700 you wrote:
> When using -Werror=missing-braces, compiler complains about missing braces.
> Let's use use ={} initialization which should do the job:
>
> tools/testing/selftests/bpf/prog_tests/sockmap_basic.c: In function 'test_sockmap_iter':
> tools/testing/selftests/bpf/prog_tests/sockmap_basic.c:181:8: error: missing braces around initializer [-Werror=missing-braces]
> union bpf_iter_link_info linfo = {0};
> ^
> tools/testing/selftests/bpf/prog_tests/sockmap_basic.c:181:8: error: (near initialization for 'linfo.map') [-Werror=missing-braces]
> tools/testing/selftests/bpf/prog_tests/sockmap_basic.c: At top level:
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: properly initialize linfo in sockmap_basic
https://git.kernel.org/bpf/bpf-next/c/48ca6243c6ad
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2020-10-02 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 0:04 [PATCH bpf-next] selftests/bpf: properly initialize linfo in sockmap_basic Stanislav Fomichev
2020-10-02 14:50 ` patchwork-bot+bpf [this message]
2020-10-02 15:59 ` John Fastabend
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=160165020267.24758.16856928754495909228.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=sdf@google.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.