From: Jiri Olsa <olsajiri@gmail.com>
To: Eder Zulian <ezulian@redhat.com>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
acme@redhat.com, vmalik@redhat.com, williams@redhat.com
Subject: Re: [PATCH v2 0/3] Fix -Wmaybe-uninitialized warnings/errors
Date: Wed, 23 Oct 2024 10:54:10 +0200 [thread overview]
Message-ID: <Zxi5stO4mWWdKqF9@krava> (raw)
In-Reply-To: <20241022172329.3871958-1-ezulian@redhat.com>
On Tue, Oct 22, 2024 at 07:23:26PM +0200, Eder Zulian wrote:
SNIP
> The above warnings and/or errors are fixed. However, they are observed with
> current default compilation options.
>
> Updates since v1:
>
> - Incorporate feedback from reviewers. Add a comment about an alternative
> patch for parse-options.c sent before (based on comments from Sam James.)
> Split in multiple patches creating this series and a typo was fixed
> "Initiazlide" -> "Initialize" (suggested by Viktor Malik). State more
> clearly that the -Wmaybe-uninitialized issues only happen when compiling
> with non-default compilation options (based on comments from Yonghong
> Song.)
>
> Thanks,
>
> Eder Zulian (3):
> resolve_btfids: Fix compiler warnings
> libbpf: Prevent compiler warnings/errors
> libsubcmd: Silence compiler warning
Acked-by: Jiri Olsa <jolsa@kernel.org>
jirka
>
> tools/bpf/resolve_btfids/main.c | 4 ++--
> tools/lib/bpf/btf_dump.c | 4 ++--
> tools/lib/subcmd/parse-options.c | 2 +-
> 3 files changed, 5 insertions(+), 5 deletions(-)
>
> --
> 2.46.2
>
next prev parent reply other threads:[~2024-10-23 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 17:23 [PATCH v2 0/3] Fix -Wmaybe-uninitialized warnings/errors Eder Zulian
2024-10-22 17:23 ` [PATCH v2 1/3] resolve_btfids: Fix compiler warnings Eder Zulian
2024-10-22 17:23 ` [PATCH v2 2/3] libbpf: Prevent compiler warnings/errors Eder Zulian
2024-10-22 17:23 ` [PATCH v2 3/3] libsubcmd: Silence compiler warning Eder Zulian
2024-10-22 23:18 ` Andrii Nakryiko
2024-10-23 21:30 ` Arnaldo Carvalho de Melo
2024-10-23 8:54 ` Jiri Olsa [this message]
2024-10-23 21:50 ` [PATCH v2 0/3] Fix -Wmaybe-uninitialized warnings/errors patchwork-bot+netdevbpf
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=Zxi5stO4mWWdKqF9@krava \
--to=olsajiri@gmail.com \
--cc=acme@redhat.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=ezulian@redhat.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=vmalik@redhat.com \
--cc=williams@redhat.com \
--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