From: kernel test robot <lkp@intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>, rafael@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, caleb.connolly@linaro.org,
lina.iyer@linaro.org, lukasz.luba@arm.com,
quic_manafm@quicinc.com, quic_priyjain@quicinc.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/2] PM: QoS: Add a performance QoS
Date: Thu, 14 Dec 2023 15:35:41 +0800 [thread overview]
Message-ID: <202312141523.Mm96MDNX-lkp@intel.com> (raw)
In-Reply-To: <20231213175818.2826876-2-daniel.lezcano@linaro.org>
Hi Daniel,
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-rc5 next-20231213]
[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/20231214-020026
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link: https://lore.kernel.org/r/20231213175818.2826876-2-daniel.lezcano%40linaro.org
patch subject: [PATCH v1 2/2] PM: QoS: Add a performance QoS
config: i386-buildonly-randconfig-002-20231214 (https://download.01.org/0day-ci/archive/20231214/202312141523.Mm96MDNX-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231214/202312141523.Mm96MDNX-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/202312141523.Mm96MDNX-lkp@intel.com/
All errors (new ones prefixed by >>):
ld: sound/soc/intel/catpt/pcm.o: in function `dev_pm_qos_hide_perf_limit':
>> pcm.c:(.text+0xb94): multiple definition of `dev_pm_qos_hide_perf_limit'; sound/soc/intel/catpt/device.o:device.c:(.text+0x624): first defined here
--
ld: sound/soc/amd/acp/acp3x-es83xx/acp3x-es83xx.o: in function `dev_pm_qos_hide_perf_limit':
>> acp3x-es83xx.c:(.text+0x368): multiple definition of `dev_pm_qos_hide_perf_limit'; sound/soc/amd/acp/acp-legacy-mach.o:acp-legacy-mach.c:(.text+0x174): first defined here
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-14 7:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 17:58 [PATCH v1 1/2] PM: QoS: Rename freq to range constraint Daniel Lezcano
2023-12-13 17:58 ` [PATCH v1 2/2] PM: QoS: Add a performance QoS Daniel Lezcano
2023-12-13 18:35 ` Caleb Connolly
2023-12-19 12:33 ` Daniel Lezcano
2023-12-14 7:23 ` kernel test robot
2023-12-14 7:35 ` kernel test robot [this message]
2024-02-12 17:30 ` Rafael J. Wysocki
2024-02-14 10:41 ` Daniel Lezcano
2024-02-15 9:39 ` Dhruva Gole
2023-12-14 9:49 ` [PATCH v1 1/2] PM: QoS: Rename freq to range constraint 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=202312141523.Mm96MDNX-lkp@intel.com \
--to=lkp@intel.com \
--cc=caleb.connolly@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=lina.iyer@linaro.org \
--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=quic_manafm@quicinc.com \
--cc=quic_priyjain@quicinc.com \
--cc=rafael@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;
as well as URLs for NNTP newsgroup(s).