From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [rcu:dev.2020.06.05a 91/92] kernel/sched/fair.c:447 find_matching_se() warn: inconsistent indenting
Date: Tue, 9 Jun 2020 11:20:21 +0800 [thread overview]
Message-ID: <202006091114.zzGQFcg5%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2067 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2020.06.05a
head: c5432e18c8bfe9283bf5e0bc5e2460ae8f39a7ee
commit: c2e2e4194231b2da0a1cc415a63220d24377381c [91/92] EXP sched: Experimental patch
config: x86_64-randconfig-m001-20200608 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
smatch warnings:
kernel/sched/fair.c:447 find_matching_se() warn: inconsistent indenting
vim +447 kernel/sched/fair.c
415
416 static void
417 find_matching_se(struct sched_entity **se, struct sched_entity **pse)
418 {
419 trace_printk("S: se: %px (%d:%px) -> %px pse: %px (%d:%px) -> %px\n",
420 *se, (*se)->depth, (*se)->cfs_rq, parent_entity(*se),
421 *pse, (*pse)->depth, (*pse)->cfs_rq, parent_entity(*pse));
422
423 /*
424 * preemption test can be made between sibling entities who are in the
425 * same cfs_rq i.e who have a common parent. Walk up the hierarchy of
426 * both tasks until we find their ancestors who are siblings of common
427 * parent.
428 */
429
430 while (!is_same_group(*se, *pse)) {
431 int se_depth = (*se)->depth;
432 int pse_depth = (*pse)->depth;
433
434 if (se_depth <= pse_depth) {
435 struct sched_entity *parent = parent_entity(*pse);
436 if (WARN_ON_ONCE(!parent))
437 return;
438 *pse = parent;
439 }
440 if (se_depth >= pse_depth) {
441 struct sched_entity *parent = parent_entity(*se);
442 if (WARN_ON_ONCE(!parent))
443 return;
444 *se = parent_entity(*se);
445 }
446
> 447 trace_printk("i: se: %px (%d:%px) -> %px pse: %px (%d:%px) -> %px\n",
448 *se, (*se)->depth, (*se)->cfs_rq, parent_entity(*se),
449 *pse, (*pse)->depth, (*pse)->cfs_rq, parent_entity(*pse));
450 }
451 }
452
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35557 bytes --]
reply other threads:[~2020-06-09 3:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202006091114.zzGQFcg5%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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
all inboxes | Powered by JetHome®