From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
kbuild@lists.01.org, lkp@intel.com, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org
Subject: Re: [kbuild] [trace:ftrace/core 35/39] kernel/trace/trace_boot.c:420 trace_boot_init_histograms() warn: curly braces intended?
Date: Fri, 3 Sep 2021 16:41:58 -0400 [thread overview]
Message-ID: <20210903164158.55debf55@gandalf.local.home> (raw)
In-Reply-To: <20210901110713.fed0ebd23c05033045953642@kernel.org>
On Wed, 1 Sep 2021 11:07:13 +0900
Masami Hiramatsu <mhiramat@kernel.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
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: kbuild-all@lists.01.org
Subject: Re: [kbuild] [trace:ftrace/core 35/39] kernel/trace/trace_boot.c:420 trace_boot_init_histograms() warn: curly braces intended?
Date: Fri, 03 Sep 2021 16:41:58 -0400 [thread overview]
Message-ID: <20210903164158.55debf55@gandalf.local.home> (raw)
In-Reply-To: <20210901110713.fed0ebd23c05033045953642@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
On Wed, 1 Sep 2021 11:07:13 +0900
Masami Hiramatsu <mhiramat@kernel.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
next prev parent reply other threads:[~2021-09-03 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 18:38 [trace:ftrace/core 35/39] kernel/trace/trace_boot.c:420 trace_boot_init_histograms() warn: curly braces intended? kernel test robot
2021-08-31 18:45 ` [kbuild] " Dan Carpenter
2021-08-31 18:45 ` Dan Carpenter
2021-09-01 2:07 ` Masami Hiramatsu
2021-09-01 2:07 ` Masami Hiramatsu
2021-09-03 20:41 ` Steven Rostedt [this message]
2021-09-03 20:41 ` Steven Rostedt
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=20210903164158.55debf55@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=dan.carpenter@oracle.com \
--cc=kbuild-all@lists.01.org \
--cc=kbuild@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mhiramat@kernel.org \
/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.