linux-kernel - Re: [kbuild] [trace:ftrace/core 35/39] kernel/trace/trace_boot.c:420 trace_boot_init_histograms() warn: curly braces intended?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20210903164158.55debf55@gandalf.local.home>
Date:   Fri, 3 Sep 2021 16:41:58 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Masami Hiramatsu <mhiramat@...nel.org>
Cc:     Dan Carpenter <dan.carpenter@...cle.com>, kbuild@...ts.01.org,
        lkp@...el.com, kbuild-all@...ts.01.org,
        linux-kernel@...r.kernel.org
Subject: Re: [kbuild] [trace:ftrace/core 35/39]
 kernel/trace/trace_boot.c:420 trace_boot_init_histograms() warn: curly
 braces intended?

On Wed, 1 Sep 2021 11:07:13 +0900
Masami Hiramatsu <mhiramat@...nel.org> wrote:

> > The missing curly braces here trigger a ball of static checker warnings.
> > I'm so happy about that.  :)  
> 
> The ftrace/core branch has a wrong version of the patch. ftrae/for-next has
> correct one. I think Steve correct this mismatch after he comes back.

Yeah, I started focusing on my ftrace/for-next branch and stopped pushing
to ftrace/core. "core" is my development branch that can rebase, "for-next"
only rebases for adding tags, but the content should seldom change.

I already sent Linus a pull request, but I'll go and fix ftrace/core now.

Thanks for letting me know.

-- Steve