From: kernel test robot <lkp@intel.com>
To: steven@liquorix.net
Cc: oe-kbuild-all@lists.linux.dev
Subject: [zen:7.2/prjc 651/740] kernel/sched/alt_sched.h:334:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
Date: Wed, 19 Aug 2026 17:27:33 +0800 [thread overview]
Message-ID: <202608191732.ytq7bc3P-lkp@intel.com> (raw)
tree: https://github.com/zen-kernel/zen-kernel 7.2/prjc
head: b735d8ec47d31db8e62d1925521a44d98c1cac2d
commit: add9dba34cde0a2265b292326f8318bf0fd733ef [651/740] sched/alt: [Sync] 6199f9999a9b sched/cputime: Handle dyntick-idle steal time correctly
config: m68k-randconfig-r122-20260819 (https://download.01.org/0day-ci/archive/20260819/202608191732.ytq7bc3P-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.4.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260819/202608191732.ytq7bc3P-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/202608191732.ytq7bc3P-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
kernel/sched/build_policy.c: note: in included file (through kernel/sched/sched.h):
>> kernel/sched/alt_sched.h:334:25: sparse: sparse: incompatible types in comparison expression (different address spaces):
kernel/sched/alt_sched.h:334:25: sparse: struct task_struct [noderef] __rcu *
kernel/sched/alt_sched.h:334:25: sparse: struct task_struct *
vim +334 kernel/sched/alt_sched.h
2f7ec82370cbb7 Alfred Chen 2019-08-19 331
e6d6a4e78f98f6 Alfred Chen 2026-01-19 332 static inline bool idle_rq(struct rq *rq)
e6d6a4e78f98f6 Alfred Chen 2026-01-19 333 {
e6d6a4e78f98f6 Alfred Chen 2026-01-19 @334 return rq->curr == rq->idle && !rq->nr_running && !rq->ttwu_pending;
e6d6a4e78f98f6 Alfred Chen 2026-01-19 335 }
e6d6a4e78f98f6 Alfred Chen 2026-01-19 336
:::::: The code at line 334 was first introduced by commit
:::::: e6d6a4e78f98f667774453eb1b15379f06183e1f sched/alt: [Sync] 1e0a2ba7afb1 sched: Provide idle_rq() helper
:::::: TO: Alfred Chen <cchalpha@gmail.com>
:::::: CC: Alfred Chen <cchalpha@gmail.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-19 9:27 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=202608191732.ytq7bc3P-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=steven@liquorix.net \
/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.