From: kernel test robot <lkp@intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 2/2] PM: QoS: Add a performance QoS
Date: Tue, 5 Dec 2023 20:40:53 +0800 [thread overview]
Message-ID: <202312052053.GM9JEd1c-lkp@intel.com> (raw)
In-Reply-To: <20231201190757.144741-2-daniel.lezcano@linaro.org>
Hi Daniel,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on rafael-pm/linux-next]
[also build test ERROR on rafael-pm/acpi-bus rafael-pm/thermal linus/master rafael-pm/devprop v6.7-rc4 next-20231205]
[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/Daniel-Lezcano/PM-QoS-Add-a-performance-QoS/20231202-031119
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link: https://lore.kernel.org/r/20231201190757.144741-2-daniel.lezcano%40linaro.org
patch subject: [RFC PATCH 2/2] PM: QoS: Add a performance QoS
config: powerpc-randconfig-002-20231203 (https://download.01.org/0day-ci/archive/20231205/202312052053.GM9JEd1c-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231205/202312052053.GM9JEd1c-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/202312052053.GM9JEd1c-lkp@intel.com/
All errors (new ones prefixed by >>):
powerpc-linux-ld: sound/aoa/core/alsa.o: in function `dev_pm_qos_hide_perf_limit':
>> alsa.c:(.text+0x230): multiple definition of `dev_pm_qos_hide_perf_limit'; sound/aoa/core/core.o:core.c:(.text+0x690): first defined here
powerpc-linux-ld: sound/aoa/core/gpio-pmf.o: in function `dev_pm_qos_hide_perf_limit':
gpio-pmf.c:(.text+0xef4): multiple definition of `dev_pm_qos_hide_perf_limit'; sound/aoa/core/core.o:core.c:(.text+0x690): first defined here
powerpc-linux-ld: sound/aoa/core/gpio-feature.o: in function `dev_pm_qos_hide_perf_limit':
gpio-feature.c:(.text+0x1ad0): multiple definition of `dev_pm_qos_hide_perf_limit'; sound/aoa/core/core.o:core.c:(.text+0x690): first defined here
--
powerpc-linux-ld: sound/aoa/soundbus/sysfs.o: in function `dev_pm_qos_hide_perf_limit':
>> sysfs.c:(.text+0x170): multiple definition of `dev_pm_qos_hide_perf_limit'; sound/aoa/soundbus/core.o:core.c:(.text+0x6d0): first defined here
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-05 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 19:07 [RFC PATCH 1/2] pm_qos: Rename freq to interval constraint Daniel Lezcano
2023-12-01 19:07 ` [RFC PATCH 2/2] PM: QoS: Add a performance QoS Daniel Lezcano
2023-12-05 12:29 ` kernel test robot
2023-12-05 12:40 ` kernel test robot [this message]
2023-12-05 14:26 ` [RFC PATCH 1/2] pm_qos: Rename freq to interval constraint kernel test robot
2023-12-08 20:42 ` Rafael J. Wysocki
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=202312052053.GM9JEd1c-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel.lezcano@linaro.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 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.