[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zxi5stO4mWWdKqF9@krava>
Date: Wed, 23 Oct 2024 10:54:10 +0200
From: Jiri Olsa <olsajiri@...il.com>
To: Eder Zulian <ezulian@...hat.com>
Cc: bpf@...r.kernel.org, linux-kernel@...r.kernel.org, ast@...nel.org,
daniel@...earbox.net, andrii@...nel.org, martin.lau@...ux.dev,
eddyz87@...il.com, song@...nel.org, yonghong.song@...ux.dev,
john.fastabend@...il.com, kpsingh@...nel.org, sdf@...ichev.me,
haoluo@...gle.com, acme@...hat.com, vmalik@...hat.com,
williams@...hat.com
Subject: Re: [PATCH v2 0/3] Fix -Wmaybe-uninitialized warnings/errors
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@...nel.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
>
Powered by blists - more mailing lists