From: kernel test robot <lkp@intel.com>
To: Lin Yikai <yikai.lin@vivo.com>,
Christian Loehle <christian.loehle@arm.com>,
Song Liu <song@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Mykola Lysenko <mykolal@fb.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kselftest@vger.kernel.org, linux-pm@vger.kernel.org,
bpf@vger.kernel.org, Tejun Heo <tj@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, zhaofuyu@vivo.com
Subject: Re: [PATCH v2 bpf-next 1/2] cpuidle: Implement BPF extensible cpuidle governor class
Date: Sun, 7 Sep 2025 14:15:33 +0800 [thread overview]
Message-ID: <202509071459.Gkqhd7YV-lkp@intel.com> (raw)
In-Reply-To: <20250901135609.76590-2-yikai.lin@vivo.com>
Hi Lin,
kernel test robot noticed the following build warnings:
[auto build test WARNING on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Lin-Yikai/cpuidle-Implement-BPF-extensible-cpuidle-governor-class/20250901-220011
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link: https://lore.kernel.org/r/20250901135609.76590-2-yikai.lin%40vivo.com
patch subject: [PATCH v2 bpf-next 1/2] cpuidle: Implement BPF extensible cpuidle governor class
config: arm-randconfig-r131-20250907 (https://download.01.org/0day-ci/archive/20250907/202509071459.Gkqhd7YV-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 8.5.0
reproduce: (https://download.01.org/0day-ci/archive/20250907/202509071459.Gkqhd7YV-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/202509071459.Gkqhd7YV-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/cpuidle/governors/ext.c:141:1: sparse: sparse: symbol 'ops_enabled_key' was not declared. Should it be static?
vim +/ops_enabled_key +141 drivers/cpuidle/governors/ext.c
139
140 static DEFINE_MUTEX(ops_mutex);
> 141 DEFINE_STATIC_KEY_FALSE(ops_enabled_key);
142 static atomic_t ops_enable_state_var = ATOMIC_INIT(OPS_DISABLED);
143
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-09-07 6:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 13:56 [PATCHSET V2 bpf-next 0/2] cpuidle, bpf: Introduce BPF-ext cpuidle governor policy via struct_ops Lin Yikai
2025-09-01 13:56 ` [PATCH v2 bpf-next 1/2] cpuidle: Implement BPF extensible cpuidle governor class Lin Yikai
2025-09-07 6:15 ` kernel test robot [this message]
2025-09-01 13:56 ` [PATCH v2 bpf-next 2/2] selftests/bpf: Add selftests for cpuidle_gov_ext Lin Yikai
2025-09-03 0:38 ` Alexei Starovoitov
2025-09-03 3:06 ` yikai.lin
2025-09-01 16:36 ` [PATCHSET V2 bpf-next 0/2] cpuidle, bpf: Introduce BPF-ext cpuidle governor policy via struct_ops Rafael J. Wysocki
2025-09-02 8:03 ` yikai.lin
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=202509071459.Gkqhd7YV-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=christian.loehle@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=sdf@fomichev.me \
--cc=skhan@linuxfoundation.org \
--cc=song@kernel.org \
--cc=tj@kernel.org \
--cc=yikai.lin@vivo.com \
--cc=yonghong.song@linux.dev \
--cc=zhaofuyu@vivo.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