From: kernel test robot <lkp@intel.com>
To: Changwoo Min <changwoo@igalia.com>,
lukasz.luba@arm.com, rafael@kernel.org, len.brown@intel.com,
pavel@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, christian.loehle@arm.com,
tj@kernel.org, kernel-dev@igalia.com, linux-pm@vger.kernel.org,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org,
Changwoo Min <changwoo@igalia.com>
Subject: Re: [PATCH v5 05/10] PM: EM: Add an iterator and accessor for the performance domain
Date: Wed, 15 Oct 2025 12:49:54 +0800 [thread overview]
Message-ID: <202510151232.UNZ2J7TZ-lkp@intel.com> (raw)
In-Reply-To: <20251014001055.772422-6-changwoo@igalia.com>
Hi Changwoo,
kernel test robot noticed the following build errors:
[auto build test ERROR on amd-pstate/linux-next]
[also build test ERROR on amd-pstate/bleeding-edge linus/master v6.18-rc1 next-20251014]
[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/Changwoo-Min/PM-EM-Assign-a-unique-ID-when-creating-a-performance-domain/20251014-082420
base: https://git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git linux-next
patch link: https://lore.kernel.org/r/20251014001055.772422-6-changwoo%40igalia.com
patch subject: [PATCH v5 05/10] PM: EM: Add an iterator and accessor for the performance domain
config: i386-buildonly-randconfig-001-20251015 (https://download.01.org/0day-ci/archive/20251015/202510151232.UNZ2J7TZ-lkp@intel.com/config)
compiler: gcc-13 (Debian 13.3.0-16) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251015/202510151232.UNZ2J7TZ-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/202510151232.UNZ2J7TZ-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/power/energy_model.c:1003:5: error: redefinition of 'for_each_em_perf_domain'
1003 | int for_each_em_perf_domain(int (*cb)(struct em_perf_domain*, void *),
| ^~~~~~~~~~~~~~~~~~~~~~~
In file included from kernel/power/energy_model.c:20:
kernel/power/em_netlink.h:18:5: note: previous definition of 'for_each_em_perf_domain' with type 'int(int (*)(struct em_perf_domain *, void *), void *)'
18 | int for_each_em_perf_domain(int (*cb)(struct em_perf_domain*, void *),
| ^~~~~~~~~~~~~~~~~~~~~~~
>> kernel/power/energy_model.c:1022:24: error: redefinition of 'em_perf_domain_get_by_id'
1022 | struct em_perf_domain *em_perf_domain_get_by_id(int id)
| ^~~~~~~~~~~~~~~~~~~~~~~~
kernel/power/em_netlink.h:24:24: note: previous definition of 'em_perf_domain_get_by_id' with type 'struct em_perf_domain *(int)'
24 | struct em_perf_domain *em_perf_domain_get_by_id(int id)
| ^~~~~~~~~~~~~~~~~~~~~~~~
vim +/for_each_em_perf_domain +1003 kernel/power/energy_model.c
1002
> 1003 int for_each_em_perf_domain(int (*cb)(struct em_perf_domain*, void *),
1004 void *data)
1005 {
1006 struct em_perf_domain *pd;
1007
1008 lockdep_assert_not_held(&em_pd_mutex);
1009 guard(mutex)(&em_pd_list_mutex);
1010
1011 list_for_each_entry(pd, &em_pd_list, node) {
1012 int ret;
1013
1014 ret = cb(pd, data);
1015 if (ret)
1016 return ret;
1017 }
1018
1019 return 0;
1020 }
1021
> 1022 struct em_perf_domain *em_perf_domain_get_by_id(int id)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-10-15 4:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 0:10 [PATCH v5 00/10] PM: EM: Add netlink support for the energy model Changwoo Min
2025-10-14 0:10 ` [PATCH v5 01/10] PM: EM: Assign a unique ID when creating a performance domain Changwoo Min
2025-10-14 8:41 ` Lukasz Luba
2025-10-14 0:10 ` [PATCH v5 02/10] PM: EM: Expose the ID of a performance domain via debugfs Changwoo Min
2025-10-14 0:10 ` [PATCH v5 03/10] PM: EM: Add em.yaml and autogen files Changwoo Min
2025-10-14 0:10 ` [PATCH v5 04/10] PM: EM: Add a skeleton code for netlink notification Changwoo Min
2025-10-14 8:43 ` Lukasz Luba
2025-10-14 0:10 ` [PATCH v5 05/10] PM: EM: Add an iterator and accessor for the performance domain Changwoo Min
2025-10-14 8:45 ` Lukasz Luba
2025-10-15 4:49 ` kernel test robot [this message]
2025-10-20 17:44 ` Rafael J. Wysocki
2025-10-20 21:35 ` Changwoo Min
2025-10-14 0:10 ` [PATCH v5 06/10] PM: EM: Implement em_nl_get_pds_doit() Changwoo Min
2025-10-14 0:10 ` [PATCH v5 07/10] PM: EM: Implement em_nl_get_pd_table_doit() Changwoo Min
2025-10-14 0:10 ` [PATCH v5 08/10] PM: EM: Implement em_notify_pd_deleted() Changwoo Min
2025-10-14 8:47 ` Lukasz Luba
2025-10-15 4:16 ` kernel test robot
2025-10-20 17:48 ` Rafael J. Wysocki
2025-10-14 0:10 ` [PATCH v5 09/10] PM: EM: Implement em_notify_pd_created/updated() Changwoo Min
2025-10-14 8:48 ` Lukasz Luba
2025-10-14 0:10 ` [PATCH v5 10/10] PM: EM: Notify an event when the performance domain changes Changwoo Min
2025-10-14 8:54 ` [PATCH v5 00/10] PM: EM: Add netlink support for the energy model Lukasz Luba
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=202510151232.UNZ2J7TZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=changwoo@igalia.com \
--cc=christian.loehle@arm.com \
--cc=kernel-dev@igalia.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=tj@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