From: Viresh Kumar <viresh.kumar@linaro.org>
To: kernel test robot <lkp@intel.com>
Cc: Zhipeng Wang <zhipeng.wang_1@nxp.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master 5324/12162] drivers/cpufreq/cpufreq-dt-platdev.c:18:34: warning: unused variable 'allowlist'
Date: Mon, 26 Jun 2023 12:23:45 +0530 [thread overview]
Message-ID: <20230626065345.2i562lyf23fantlm@vireshk-i7> (raw)
In-Reply-To: <202306250025.savpMM8L-lkp@intel.com>
On 25-06-23, 00:28, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 8d2be868b42c08290509c60515865f4de24ea704
> commit: 3b062a086984d35a3c6d3a1c7841d0aa73aa76af [5324/12162] cpufreq: dt-platdev: Support building as module
> config: i386-randconfig-r035-20230624 (https://download.01.org/0day-ci/archive/20230625/202306250025.savpMM8L-lkp@intel.com/config)
> compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project.git 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
> reproduce: (https://download.01.org/0day-ci/archive/20230625/202306250025.savpMM8L-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/202306250025.savpMM8L-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> >> drivers/cpufreq/cpufreq-dt-platdev.c:18:34: warning: unused variable 'allowlist' [-Wunused-const-variable]
> static const struct of_device_id allowlist[] __initconst = {
> ^
> >> drivers/cpufreq/cpufreq-dt-platdev.c:105:34: warning: unused variable 'blocklist' [-Wunused-const-variable]
> static const struct of_device_id blocklist[] __initconst = {
> ^
> 2 warnings generated.
>
Hi,
Do you have any patch to fix this ? I am not sure why the error is coming here
and I am not able to reproduce it too.
--
viresh
next prev parent reply other threads:[~2023-06-26 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 16:28 kernel test robot
2023-06-26 6:53 ` Viresh Kumar [this message]
2023-06-28 1:33 ` [EXT] " Zhipeng Wang
2023-06-28 15:39 ` Nathan Chancellor
2023-06-30 6:06 ` Viresh Kumar
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=20230626065345.2i562lyf23fantlm@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=zhipeng.wang_1@nxp.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