From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android17-6.18 1/1] kernel/sched/core.c:3981:2: error: implicit declaration of function '__do_migrate_task_rq'; did you mean '__migrate_task'?
Date: Fri, 06 Nov 2026 07:05:17 +0100 [thread overview]
Message-ID: <202611060725.SQ0aNff9-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android17-6.18
head: b835509d43ba8175031f800f12347f8e8206a471
commit: b835509d43ba8175031f800f12347f8e8206a471 [1/1] ANDROID: sched/proxy_exec: Invoke migrate_task_rq() on proxy-migration
config: arm-randconfig-r2109-20261106 (https://download.01.org/0day-ci/archive/20261106/202611060725.SQ0aNff9-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261106/202611060725.SQ0aNff9-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/202611060725.SQ0aNff9-lkp@intel.com/
All errors (new ones prefixed by >>):
kernel/sched/core.c: In function 'proxy_set_task_cpu':
>> kernel/sched/core.c:3981:2: error: implicit declaration of function '__do_migrate_task_rq'; did you mean '__migrate_task'? [-Werror=implicit-function-declaration]
3981 | __do_migrate_task_rq(p, cpu);
| ^~~~~~~~~~~~~~~~~~~~
| __migrate_task
cc1: some warnings being treated as errors
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for DRM_MIPI_DSI
Depends on [n]: HAS_IOMEM [=y] && DRM [=n]
Selected by [y]:
- GKI_HIDDEN_DRM_CONFIGS [=y]
WARNING: unmet direct dependencies detected for BALLOON_COMPACTION
Depends on [n]: COMPACTION [=n] && MEMORY_BALLOON [=y]
Selected by [y]:
- GKI_HIDDEN_MM_CONFIGS [=y]
WARNING: unmet direct dependencies detected for WIRELESS_EXT
Depends on [n]: NET [=n] && WIRELESS [=n]
Selected by [y]:
- GKI_LEGACY_WEXT_ALLCONFIG [=y]
WARNING: unmet direct dependencies detected for WEXT_CORE
Depends on [n]: NET [=n] && WIRELESS [=n] && (CFG80211_WEXT [=n] || WIRELESS_EXT [=y])
Selected by [y]:
- GKI_LEGACY_WEXT_ALLCONFIG [=y]
WARNING: unmet direct dependencies detected for WEXT_PROC
Depends on [n]: NET [=n] && WIRELESS [=n] && PROC_FS [=y] && WEXT_CORE [=y]
Selected by [y]:
- GKI_LEGACY_WEXT_ALLCONFIG [=y]
WARNING: unmet direct dependencies detected for WEXT_PRIV
Depends on [n]: NET [=n] && WIRELESS [=n]
Selected by [y]:
- GKI_LEGACY_WEXT_ALLCONFIG [=y]
vim +3981 kernel/sched/core.c
3969
3970 static inline void proxy_set_task_cpu(struct task_struct *p, int cpu)
3971 {
3972 unsigned int wake_cpu;
3973
3974 /*
3975 * Since we are enqueuing a blocked task on a cpu it may
3976 * not be able to run on, preserve wake_cpu when we
3977 * __set_task_cpu so we can return the task to where it
3978 * was previously runnable.
3979 */
3980 wake_cpu = p->wake_cpu;
> 3981 __do_migrate_task_rq(p, cpu);
3982 __set_task_cpu(p, cpu);
3983 p->wake_cpu = wake_cpu;
3984 }
3985
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-11-06 6:05 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=202611060725.SQ0aNff9-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.