From: kernel test robot <lkp@intel.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] sched/fair: Encapsulate set custom slice in a __setparam_fair() function
Date: Sat, 11 Jan 2025 17:27:00 +0800 [thread overview]
Message-ID: <202501111759.lr8LHoZu-lkp@intel.com> (raw)
In-Reply-To: <20250110144656.484601-1-vincent.guittot@linaro.org>
Hi Vincent,
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/sched/core]
[also build test ERROR on linus/master v6.13-rc6 next-20250110]
[cannot apply to peterz-queue/sched/core]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Vincent-Guittot/sched-fair-Encapsulate-set-custom-slice-in-a-__setparam_fair-function/20250110-225327
base: tip/sched/core
patch link: https://lore.kernel.org/r/20250110144656.484601-1-vincent.guittot%40linaro.org
patch subject: [PATCH] sched/fair: Encapsulate set custom slice in a __setparam_fair() function
config: arc-allnoconfig (https://download.01.org/0day-ci/archive/20250111/202501111759.lr8LHoZu-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250111/202501111759.lr8LHoZu-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/202501111759.lr8LHoZu-lkp@intel.com/
All errors (new ones prefixed by >>):
arc-elf-ld: kernel/sched/build_policy.o: in function `__sched_setscheduler':
build_policy.c:(.text+0x41be): undefined reference to `__setparam_fair'
>> arc-elf-ld: build_policy.c:(.text+0x41be): undefined reference to `__setparam_fair'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-01-11 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 14:46 [PATCH] sched/fair: Encapsulate set custom slice in a __setparam_fair() function Vincent Guittot
2025-01-10 15:14 ` Phil Auld
2025-01-10 16:58 ` Peter Zijlstra
2025-01-10 17:16 ` Vincent Guittot
2025-01-11 9:27 ` kernel test robot [this message]
2025-01-11 9:48 ` kernel test robot
2025-01-15 9:17 ` [tip: sched/core] " tip-bot2 for Vincent Guittot
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=202501111759.lr8LHoZu-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vincent.guittot@linaro.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.