From: Konrad Dybcio <konrad.dybcio@somainline.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: [linux-next:master 10841/11508] drivers/clk/qcom/gcc-sm6350.c:179:37: warning: unused variable 'gcc_parent_data_2'
Date: Thu, 2 Sep 2021 11:01:30 +0200 [thread overview]
Message-ID: <85c61a79-3e83-84c8-1b75-3e4640ac3490@somainline.org> (raw)
In-Reply-To: <202109021640.TXyMlULd-lkp@intel.com>
On 02.09.2021 10:57, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 34560ced20599a01660a693f464c7c7dc83db1d9
> commit: 131abae905df99f63d825e47b4df100d34f518ce [10841/11508] clk: qcom: Add SM6350 GCC driver
> config: riscv-buildonly-randconfig-r006-20210902 (attached as .config)
> compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project c9948e9254fbb6ea00f66c7b4542311d21e060be)
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # install riscv cross compiling tool for clang build
> # apt-get install binutils-riscv64-linux-gnu
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=131abae905df99f63d825e47b4df100d34f518ce
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout 131abae905df99f63d825e47b4df100d34f518ce
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=riscv
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
>>> drivers/clk/qcom/gcc-sm6350.c:179:37: warning: unused variable 'gcc_parent_data_2' [-Wunused-const-variable]
> static const struct clk_parent_data gcc_parent_data_2[] = {
> ^
> 1 warning generated.
>
>
> vim +/gcc_parent_data_2 +179 drivers/clk/qcom/gcc-sm6350.c
>
> 178
> > 179 static const struct clk_parent_data gcc_parent_data_2[] = {
> 180 { .fw_name = "bi_tcxo" },
> 181 { .hw = &gpll0_out_odd.clkr.hw },
> 182 };
> 183 static const struct clk_parent_data gcc_parent_data_2_ao[] = {
> 184 { .fw_name = "bi_tcxo_ao" },
> 185 { .hw = &gpll0_out_odd.clkr.hw },
> 186 };
> 187
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
Looks like this slipped through.. gcc_parent_data_2[] is in fact not used. Could you remove that array in your tree, Stephen?
Konrad
next prev parent reply other threads:[~2021-09-02 9:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 8:57 kernel test robot
2021-09-02 9:01 ` Konrad Dybcio [this message]
2021-09-03 0:21 ` Stephen Boyd
2021-09-03 10:19 ` Konrad Dybcio
2021-09-03 18:16 ` Stephen Boyd
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=85c61a79-3e83-84c8-1b75-3e4640ac3490@somainline.org \
--to=konrad.dybcio@somainline.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=sboyd@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