From: kernel test robot <lkp@intel.com>
To: Jie Zhan <zhanjie9@hisilicon.com>,
ionela.voinescu@arm.com, beata.michalska@arm.com,
wangxiongfeng2@huawei.com, viresh.kumar@linaro.org,
rafael@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-pm@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linuxarm@huawei.com,
zhanjie9@hisilicon.com, jonathan.cameron@huawei.com,
wanghuiqiang@huawei.com, zhenglifeng1@huawei.com,
lihuisong@huawei.com, yangyicong@huawei.com,
liaochang1@huawei.com, zengheng4@huawei.com
Subject: Re: [PATCH v2 3/3] cppc_cpufreq: Remove HiSilicon CPPC workaround
Date: Sat, 14 Sep 2024 20:13:50 +0800 [thread overview]
Message-ID: <202409141923.kDxHsCjn-lkp@intel.com> (raw)
In-Reply-To: <20240912072231.439332-4-zhanjie9@hisilicon.com>
Hi Jie,
kernel test robot noticed the following build warnings:
[auto build test WARNING on rafael-pm/linux-next]
[also build test WARNING on rafael-pm/bleeding-edge linus/master v6.11-rc7 next-20240913]
[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/Jie-Zhan/cppc_cpufreq-Return-desired-perf-in-get-if-feedback-counters-are-0/20240912-153059
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link: https://lore.kernel.org/r/20240912072231.439332-4-zhanjie9%40hisilicon.com
patch subject: [PATCH v2 3/3] cppc_cpufreq: Remove HiSilicon CPPC workaround
config: arm64-randconfig-001-20240913 (https://download.01.org/0day-ci/archive/20240914/202409141923.kDxHsCjn-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240914/202409141923.kDxHsCjn-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/202409141923.kDxHsCjn-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/cpufreq/cppc_cpufreq.c:45:3: warning: unused variable 'fie_disabled' [-Wunused-variable]
} fie_disabled = FIE_UNSET;
^
1 warning generated.
vim +/fie_disabled +45 drivers/cpufreq/cppc_cpufreq.c
a3f083e04a8766 Zheng Bin 2022-05-21 40
ae2df912d1a557 Jeremy Linton 2022-09-12 41 static enum {
ae2df912d1a557 Jeremy Linton 2022-09-12 42 FIE_UNSET = -1,
ae2df912d1a557 Jeremy Linton 2022-09-12 43 FIE_ENABLED,
ae2df912d1a557 Jeremy Linton 2022-09-12 44 FIE_DISABLED
ae2df912d1a557 Jeremy Linton 2022-09-12 @45 } fie_disabled = FIE_UNSET;
ae2df912d1a557 Jeremy Linton 2022-09-12 46
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-14 12:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 7:22 [PATCH v2 0/3] cppc_cpufreq: Rework ->get() error handling when cores are idle Jie Zhan
2024-09-12 7:22 ` [PATCH v2 1/3] cppc_cpufreq: Return desired perf in ->get() if feedback counters are 0 Jie Zhan
2024-09-12 9:43 ` Ionela Voinescu
2024-09-13 12:05 ` Jie Zhan
2024-09-17 10:36 ` Ionela Voinescu
2024-09-18 2:05 ` Jie Zhan
2024-09-18 10:15 ` Ionela Voinescu
2024-09-19 1:17 ` Jie Zhan
2024-09-12 7:22 ` [PATCH v2 2/3] cppc_cpufreq: Return latest desired perf if feedback counters don't change Jie Zhan
2024-09-12 7:22 ` [PATCH v2 3/3] cppc_cpufreq: Remove HiSilicon CPPC workaround Jie Zhan
2024-09-14 12:13 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-12 7:19 [PATCH v2 0/3] cppc_cpufreq: Rework ->get() error handling when cores are idle Jie Zhan
2024-09-12 7:20 ` [PATCH v2 3/3] cppc_cpufreq: Remove HiSilicon CPPC workaround Jie Zhan
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=202409141923.kDxHsCjn-lkp@intel.com \
--to=lkp@intel.com \
--cc=beata.michalska@arm.com \
--cc=ionela.voinescu@arm.com \
--cc=jonathan.cameron@huawei.com \
--cc=liaochang1@huawei.com \
--cc=lihuisong@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=wanghuiqiang@huawei.com \
--cc=wangxiongfeng2@huawei.com \
--cc=yangyicong@huawei.com \
--cc=zengheng4@huawei.com \
--cc=zhanjie9@hisilicon.com \
--cc=zhenglifeng1@huawei.com \
/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