From: kernel test robot <lkp@intel.com>
To: Kalesh Singh <kaleshsingh@google.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>
Subject: [PATCH] tracing/histogram: fix semicolon.cocci warnings
Date: Sat, 30 Oct 2021 08:56:15 +0800 [thread overview]
Message-ID: <20211030005615.GA41257@3074f0d39c61> (raw)
In-Reply-To: <202110300854.vlngoEsM-lkp@intel.com>
From: kernel test robot <lkp@intel.com>
kernel/trace/trace_events_hist.c:6039:2-3: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
Fixes: c5eac6ee8bc5 ("tracing/histogram: Simplify handling of .sym-offset in expressions")
CC: Kalesh Singh <kaleshsingh@google.com>
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git for-next
head: 93d76e4a0e0112b320c4f0e2a3930ad634628c58
commit: c5eac6ee8bc5d32e48b3845472b547574061f49f [91/100] tracing/histogram: Simplify handling of .sym-offset in expressions
:::::: branch date: 24 hours ago
:::::: commit date: 3 days ago
trace_events_hist.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/kernel/trace/trace_events_hist.c
+++ b/kernel/trace/trace_events_hist.c
@@ -6036,7 +6036,7 @@ static int event_hist_trigger_func(struc
while (start) {
*(start + 4) = 'X';
start = strstr(start + 11, ".sym-offset");
- };
+ }
attrs = parse_hist_trigger_attrs(file->tr, trigger);
if (IS_ERR(attrs))
prev parent reply other threads:[~2021-10-30 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 0:56 [rostedt-trace:for-next 91/100] kernel/trace/trace_events_hist.c:6039:2-3: Unneeded semicolon kernel test robot
2021-10-30 0:56 ` kernel test robot [this message]
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=20211030005615.GA41257@3074f0d39c61 \
--to=lkp@intel.com \
--cc=kaleshsingh@google.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®