From: kernel test robot <lkp@intel.com>
To: Ajit Pandey <quic_ajipan@quicinc.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Taniya Das <quic_tdas@quicinc.com>,
Jagadeesh Kona <quic_jkona@quicinc.com>,
Imran Shaik <quic_imrashai@quicinc.com>,
Satya Priya Kakitapalli <quic_skakitap@quicinc.com>,
Ajit Pandey <quic_ajipan@quicinc.com>
Subject: Re: [PATCH 7/7] clk: qcom: Add GPUCC driver support for SM4450
Date: Tue, 2 Apr 2024 17:59:43 +0800 [thread overview]
Message-ID: <202404021747.ie04rWAv-lkp@intel.com> (raw)
In-Reply-To: <20240330182817.3272224-8-quic_ajipan@quicinc.com>
Hi Ajit,
kernel test robot noticed the following build warnings:
[auto build test WARNING on clk/clk-next]
[also build test WARNING on robh/for-next linus/master v6.9-rc2 next-20240402]
[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/Ajit-Pandey/clk-qcom-clk-alpha-pll-Fix-CAL_L_VAL-override-for-LUCID-EVO-PLL/20240331-023329
base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next
patch link: https://lore.kernel.org/r/20240330182817.3272224-8-quic_ajipan%40quicinc.com
patch subject: [PATCH 7/7] clk: qcom: Add GPUCC driver support for SM4450
config: powerpc64-randconfig-r132-20240402 (https://download.01.org/0day-ci/archive/20240402/202404021747.ie04rWAv-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 546dc2245ffc4cccd0b05b58b7a5955e355a3b27)
reproduce: (https://download.01.org/0day-ci/archive/20240402/202404021747.ie04rWAv-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/202404021747.ie04rWAv-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/clk/qcom/gpucc-sm4450.c:740:10: sparse: sparse: Initializer entry defined twice
drivers/clk/qcom/gpucc-sm4450.c:746:10: sparse: also defined here
vim +740 drivers/clk/qcom/gpucc-sm4450.c
736
737 static const struct qcom_reset_map gpu_cc_sm4450_resets[] = {
738 [GPU_CC_CB_BCR] = { 0x93a0 },
739 [GPU_CC_CX_BCR] = { 0x9104 },
> 740 [GPU_CC_GX_BCR] = { 0x9058 },
741 [GPU_CC_FAST_HUB_BCR] = { 0x93e4 },
742 [GPU_CC_ACD_BCR] = { 0x9358 },
743 [GPU_CC_FF_BCR] = { 0x9470 },
744 [GPU_CC_GFX3D_AON_BCR] = { 0x9198 },
745 [GPU_CC_GMU_BCR] = { 0x9314 },
746 [GPU_CC_GX_BCR] = { 0x9058 },
747 [GPU_CC_RBCPR_BCR] = { 0x91e0 },
748 [GPU_CC_XO_BCR] = { 0x9000 },
749 [GPU_CC_GX_ACD_IROOT_BCR] = { 0x958c },
750 };
751
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-04-02 10:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 18:28 [PATCH 0/7] clk: qcom: Add support for DISPCC, CAMCC and GPUCC on SM4450 Ajit Pandey
2024-03-30 18:28 ` [PATCH 1/7] clk: qcom: clk-alpha-pll: Fix CAL_L_VAL override for LUCID EVO PLL Ajit Pandey
2024-03-30 19:19 ` Krzysztof Kozlowski
2024-04-02 18:35 ` Ajit Pandey
2024-04-03 6:49 ` Krzysztof Kozlowski
2024-04-03 8:37 ` Dmitry Baryshkov
2024-04-03 8:50 ` Krzysztof Kozlowski
2024-04-03 11:07 ` Ajit Pandey
2024-03-30 18:28 ` [PATCH 2/7] dt-bindings: clock: qcom: Add DISPCC clocks for SM4450 Ajit Pandey
2024-03-31 8:17 ` Krzysztof Kozlowski
2024-04-04 7:04 ` Ajit Pandey
2024-04-04 7:08 ` Krzysztof Kozlowski
2024-03-30 18:28 ` [PATCH 3/7] clk: qcom: Add DISPCC driver support " Ajit Pandey
2024-03-31 1:28 ` Dmitry Baryshkov
2024-04-02 18:16 ` Ajit Pandey
2024-03-30 18:28 ` [PATCH 4/7] dt-bindings: clock: qcom: Add CAMCC clocks " Ajit Pandey
2024-03-31 8:18 ` Krzysztof Kozlowski
2024-03-30 18:28 ` [PATCH 5/7] clk: qcom: Add CAMCC driver support " Ajit Pandey
2024-03-31 1:36 ` Dmitry Baryshkov
2024-03-30 18:28 ` [PATCH 6/7] dt-bindings: clock: qcom: Add GPUCC clocks " Ajit Pandey
2024-03-31 8:18 ` Krzysztof Kozlowski
2024-03-31 8:30 ` Krzysztof Kozlowski
2024-04-02 18:29 ` Ajit Pandey
2024-03-30 18:28 ` [PATCH 7/7] clk: qcom: Add GPUCC driver support " Ajit Pandey
2024-03-31 1:39 ` Dmitry Baryshkov
2024-04-02 18:25 ` Ajit Pandey
2024-04-02 19:23 ` Dmitry Baryshkov
2024-04-03 10:49 ` Ajit Pandey
2024-04-03 10:52 ` Dmitry Baryshkov
2024-04-03 11:59 ` Ajit Pandey
2024-04-02 9:59 ` kernel test robot [this message]
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=202404021747.ie04rWAv-lkp@intel.com \
--to=lkp@intel.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_ajipan@quicinc.com \
--cc=quic_imrashai@quicinc.com \
--cc=quic_jkona@quicinc.com \
--cc=quic_skakitap@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=vkoul@kernel.org \
--cc=vladimir.zapolskiy@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.