From: kernel test robot <lkp@intel.com>
To: quic_vamslank@quicinc.com, agross@kernel.org,
bjorn.andersson@linaro.org, mturquette@baylibre.com,
sboyd@kernel.org, robh+dt@kernel.org, tglx@linutronix.de,
maz@kernel.org
Cc: kbuild-all@lists.01.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 3/6] clk: qcom: Add SDX65 GCC support
Date: Mon, 8 Nov 2021 22:29:46 +0800 [thread overview]
Message-ID: <202111082209.d5dqqHkK-lkp@intel.com> (raw)
In-Reply-To: <1635552042-16250-4-git-send-email-quic_vamslank@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 2451 bytes --]
Hi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on clk/clk-next]
[also build test ERROR on robh/for-next tip/irq/core v5.15 next-20211108]
[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]
url: https://github.com/0day-ci/linux/commits/quic_vamslank-quicinc-com/Add-Pdc-GCC-and-RPMh-clock-support-for-SDX65/20211030-080125
base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next
config: openrisc-buildonly-randconfig-r003-20211031 (attached as .config)
compiler: or1k-linux-gcc (GCC) 11.2.0
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
# https://github.com/0day-ci/linux/commit/8326e7436c674aa934aa91444cb9f201b37a8da1
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review quic_vamslank-quicinc-com/Add-Pdc-GCC-and-RPMh-clock-support-for-SDX65/20211030-080125
git checkout 8326e7436c674aa934aa91444cb9f201b37a8da1
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=openrisc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/clk/qcom/gcc-sdx65.c:94:37: error: 'gcc_parent_data_1' defined but not used [-Werror=unused-const-variable=]
94 | static const struct clk_parent_data gcc_parent_data_1[] = {
| ^~~~~~~~~~~~~~~~~
>> drivers/clk/qcom/gcc-sdx65.c:90:32: error: 'gcc_parent_map_1' defined but not used [-Werror=unused-const-variable=]
90 | static const struct parent_map gcc_parent_map_1[] = {
| ^~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/gcc_parent_data_1 +94 drivers/clk/qcom/gcc-sdx65.c
89
> 90 static const struct parent_map gcc_parent_map_1[] = {
91 { P_BI_TCXO, 0 },
92 };
93
> 94 static const struct clk_parent_data gcc_parent_data_1[] = {
95 { .fw_name = "bi_tcxo" },
96 };
97
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30695 bytes --]
next prev parent reply other threads:[~2021-11-08 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 0:00 [PATCH v3 0/6] Add Pdc, GCC and RPMh clock support for SDX65 quic_vamslank
2021-10-30 0:00 ` [PATCH v3 1/6] dt-bindings: clock: Add SDX65 GCC clock bindings quic_vamslank
2021-10-31 14:16 ` Rob Herring
2021-10-30 0:00 ` [PATCH v3 2/6] clk: qcom: Add LUCID_EVO PLL type for SDX65 quic_vamslank
2021-10-30 0:00 ` [PATCH v3 3/6] clk: qcom: Add SDX65 GCC support quic_vamslank
2021-11-08 14:29 ` kernel test robot [this message]
2021-10-30 0:00 ` [PATCH v3 4/6] dt-bindings: clock: Introduce RPMHCC bindings for SDX65 quic_vamslank
2021-10-30 0:00 ` [PATCH v3 5/6] clk: qcom: Add support for SDX65 RPMh clocks quic_vamslank
2021-10-30 0:00 ` [PATCH v3 6/6] dt-bindings: clock: Introduce pdc bindings for SDX65 quic_vamslank
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=202111082209.d5dqqHkK-lkp@intel.com \
--to=lkp@intel.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_vamslank@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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).