From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [PATCH] sched: fix semicolon.cocci warnings
Date: Tue, 30 Mar 2021 00:18:40 +0800 [thread overview]
Message-ID: <20210329161840.GA13882@71f464c0f9b2> (raw)
In-Reply-To: <202103300031.ytxjsLar-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
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: b0f0fca868fe ("sched: prctl() cookie manipulation for core scheduling")
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/peterz/queue.git sched/core-sched
head: 08af27c612f37a9b048e9e53cf75c5fa747015a1
commit: b0f0fca868fe5cb9b94963cf749154830f013ed9 [23/24] sched: prctl() cookie manipulation for core scheduling
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);
next prev parent reply other threads:[~2021-03-29 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 16:18 [peterz-queue:sched/core-sched 23/24] kernel/sched/core_sched.c:201:2-3: Unneeded semicolon kernel test robot
2021-03-29 16:18 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-17 20:14 [tip:sched/core 28/29] " kernel test robot
2021-06-17 20:14 ` [PATCH] sched: fix semicolon.cocci warnings kernel test robot
2021-06-17 20:14 ` kernel test robot
2018-05-02 15:11 [PATCH net-next v7 1/7] sched: Add Common Applications Kept Enhanced (cake) qdisc Toke Høiland-Jørgensen
2018-05-03 5:05 ` [PATCH] sched: fix semicolon.cocci warnings kbuild 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=20210329161840.GA13882@71f464c0f9b2 \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.