From: kernel test robot <lkp@intel.com>
To: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [mhiramat:topic/fgraph-multi 3/15] checkpatch: WARNING: braces {} are not necessary for single statement blocks
Date: Mon, 23 Oct 2023 00:12:11 +0800 [thread overview]
Message-ID: <202310230045.UQMPTPFZ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mhiramat/linux.git topic/fgraph-multi
head: 7b4f1147ab12cc7de50a7a15d6a818b02a0e4fa2
commit: 235c778d489b69addce14b2fd9da088bb6c21156 [3/15] function_graph: Add an array structure that will allow multiple callbacks
reproduce: (https://download.01.org/0day-ci/archive/20231023/202310230045.UQMPTPFZ-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202310230045.UQMPTPFZ-lkp@intel.com/
# many are suggestions rather than must-fix
WARNING:BRACES: braces {} are not necessary for single statement blocks
#104: FILE: kernel/trace/fgraph.c:675:
+ for (i = 0; i < FGRAPH_ARRAY_SIZE; i++) {
+ fgraph_array[i] = &fgraph_stub;
+ }
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-10-22 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 16:12 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-15 16:06 [mhiramat:topic/fgraph-multi 3/15] checkpatch: WARNING: braces {} are not necessary for single statement blocks kernel test robot
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=202310230045.UQMPTPFZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.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.