From: kernel test robot <lkp@intel.com>
To: Chris Hyser <chris.hyser@oracle.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>
Subject: [PATCH] sched: fix semicolon.cocci warnings
Date: Fri, 18 Jun 2021 04:14:39 +0800 [thread overview]
Message-ID: <20210617201439.GA17372@b4e38bc61117> (raw)
In-Reply-To: <202106180450.8bfm8BDW-lkp@intel.com>
From: kernel test robot <lkp@intel.com>
kernel/sched/core_sched.c:201:2-3: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
Fixes: 7ac592aa35a6 ("sched: prctl() core-scheduling interface")
CC: Chris Hyser <chris.hyser@oracle.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/tip/tip.git sched/core
head: 9f26990074931bbf797373e53104216059b300b1
commit: 7ac592aa35a684ff1858fb9ec282886b9e3575ac [28/29] sched: prctl() core-scheduling interface
:::::: branch date: 5 weeks ago
:::::: commit date: 5 weeks ago
core_sched.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/kernel/sched/core_sched.c
+++ b/kernel/sched/core_sched.c
@@ -198,7 +198,7 @@ int sched_core_share_pid(unsigned int cm
default:
err = -EINVAL;
goto out;
- };
+ }
if (type == PIDTYPE_PID) {
__sched_core_set(task, cookie);
prev parent reply other threads:[~2021-06-17 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 20:14 [tip:sched/core 28/29] kernel/sched/core_sched.c:201:2-3: Unneeded semicolon kernel test robot
2021-06-17 20:14 ` 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=20210617201439.GA17372@b4e38bc61117 \
--to=lkp@intel.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=chris.hyser@oracle.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox