All of lore.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
Subject: Re: [PATCH bpf-next] selftests/bpf: Fix RELEASE build failure with gcc14
Date: Tue, 17 Jun 2025 18:15:08 +0000	[thread overview]
Message-ID: <175018410874.3219184.1011690780572987225.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250617044956.2686668-1-yonghong.song@linux.dev>

Hello:

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

On Mon, 16 Jun 2025 21:49:56 -0700 you wrote:
> With gcc14, when building with RELEASE=1, I hit four below compilation
> failure:
> 
> Error 1:
>   In file included from test_loader.c:6:
>   test_loader.c: In function ‘run_subtest’: test_progs.h:194:17:
>       error: ‘retval’ may be used uninitialized in this function
>    [-Werror=maybe-uninitialized]
>     194 |                 fprintf(stdout, ##format);           \
>         |                 ^~~~~~~
>   test_loader.c:958:13: note: ‘retval’ was declared here
>     958 |         int retval, err, i;
>         |             ^~~~~~
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Fix RELEASE build failure with gcc14
    https://git.kernel.org/bpf/bpf-next/c/a633dab4b4d2

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



      parent reply	other threads:[~2025-06-17 18:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17  4:49 [PATCH bpf-next] selftests/bpf: Fix RELEASE build failure with gcc14 Yonghong Song
2025-06-17 17:24 ` Alexei Starovoitov
2025-06-17 22:09   ` Yonghong Song
2025-06-17 18:15 ` 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=175018410874.3219184.1011690780572987225.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=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 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.