From: kernel test robot <lkp@intel.com>
To: "Dhaval Giani (AMD)" <dhaval@gianis.ca>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Dhaval Giani <dhaval.giani@amd.com>,
Gautham Shenoy <gautham.shenoy@amd.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
"Dhaval Giani (AMD)" <dhaval@gianis.ca>
Subject: Re: [PATCH 1/3] sched/fair: Introduce a new debugfs directory for EEVDF tests
Date: Wed, 7 May 2025 14:56:23 +0800 [thread overview]
Message-ID: <202505071441.9cwPFBsc-lkp@intel.com> (raw)
In-Reply-To: <20250422-b4-eevdf-tests-v1-post-v1-1-5b174f040f55@gianis.ca>
Hi Dhaval,
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/sched/core]
[also build test ERROR on linus/master v6.15-rc5 next-20250506]
[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/Dhaval-Giani-AMD/sched-fair-Add-a-test-to-test-that-a-task-selected-to-run-has-positive-lag/20250423-081648
base: tip/sched/core
patch link: https://lore.kernel.org/r/20250422-b4-eevdf-tests-v1-post-v1-1-5b174f040f55%40gianis.ca
patch subject: [PATCH 1/3] sched/fair: Introduce a new debugfs directory for EEVDF tests
config: arc-allnoconfig (https://download.01.org/0day-ci/archive/20250507/202505071441.9cwPFBsc-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250507/202505071441.9cwPFBsc-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/202505071441.9cwPFBsc-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from kernel/sched/build_utility.c:71:
kernel/sched/debug.c: In function 'sched_init_debug':
>> kernel/sched/debug.c:539:9: error: implicit declaration of function 'debugfs_eevdf_testing_init' [-Wimplicit-function-declaration]
539 | debugfs_eevdf_testing_init(debugfs_sched);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/debugfs_eevdf_testing_init +539 kernel/sched/debug.c
534
535 debugfs_create_file("debug", 0444, debugfs_sched, NULL, &sched_debug_fops);
536
537 debugfs_fair_server_init();
538
> 539 debugfs_eevdf_testing_init(debugfs_sched);
540
541 return 0;
542 }
543 late_initcall(sched_init_debug);
544
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-07 6:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 0:15 Dhaval Giani (AMD)
2025-05-07 6:56 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-23 0:20 [PATCH 0/3] sched/eevdf: Introduce functional invariants for EEVDF Dhaval Giani (AMD)
2025-04-23 0:20 ` [PATCH 1/3] sched/fair: Introduce a new debugfs directory for EEVDF tests Dhaval Giani (AMD)
2025-05-07 10:03 ` kernel test robot
2025-04-23 0:10 [PATCH 0/3] sched/eevdf: Introduce functional invariants for EEVDF Dhaval Giani (AMD)
2025-04-23 0:11 ` [PATCH 1/3] sched/fair: Introduce a new debugfs directory for EEVDF tests Dhaval Giani (AMD)
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=202505071441.9cwPFBsc-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhaval.giani@amd.com \
--cc=dhaval@gianis.ca \
--cc=gautham.shenoy@amd.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--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 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®