public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org,
	lkp@intel.com
Subject: Re: [PATCH bpf-next 1/2] bpf: Fix compilation warning with -Wparentheses
Date: Fri, 28 Jul 2023 16:00:21 +0000	[thread overview]
Message-ID: <169056002190.17152.2704300359734171993.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230728055740.2284534-1-yonghong.song@linux.dev>

Hello:

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

On Thu, 27 Jul 2023 22:57:40 -0700 you wrote:
> The kernel test robot reported compilation warnings when -Wparentheses is
> added to KBUILD_CFLAGS with gcc compiler. The following is the error message:
> 
>   .../bpf-next/kernel/bpf/verifier.c: In function ‘coerce_reg_to_size_sx’:
>   .../bpf-next/kernel/bpf/verifier.c:5901:14:
>     error: suggest parentheses around comparison in operand of ‘==’ [-Werror=parentheses]
>     if (s64_max >= 0 == s64_min >= 0) {
>         ~~~~~~~~^~~~
>   .../bpf-next/kernel/bpf/verifier.c: In function ‘coerce_subreg_to_size_sx’:
>   .../bpf-next/kernel/bpf/verifier.c:5965:14:
>     error: suggest parentheses around comparison in operand of ‘==’ [-Werror=parentheses]
>     if (s32_min >= 0 == s32_max >= 0) {
>         ~~~~~~~~^~~~
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] bpf: Fix compilation warning with -Wparentheses
    https://git.kernel.org/bpf/bpf-next/c/09fedc731874
  - [bpf-next,2/2] selftests/bpf: Enable test test_progs-cpuv4 for gcc build kernel
    https://git.kernel.org/bpf/bpf-next/c/a76584fc9ff6

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-07-28 16:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28  5:57 [PATCH bpf-next 1/2] bpf: Fix compilation warning with -Wparentheses Yonghong Song
2023-07-28  5:57 ` [PATCH bpf-next 2/2] selftests/bpf: Enable test test_progs-cpuv4 for gcc build kernel Yonghong Song
2023-07-28 10:25 ` [PATCH bpf-next 1/2] bpf: Fix compilation warning with -Wparentheses Jiri Olsa
2023-07-28 16: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=169056002190.17152.2704300359734171993.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=kernel-team@fb.com \
    --cc=lkp@intel.com \
    --cc=martin.lau@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