From: kernel test robot <lkp@intel.com>
To: srinivas.kandagatla@linaro.org, andersson@kernel.org,
linus.walleij@linaro.org
Cc: oe-kbuild-all@lists.linux.dev, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
srinivas.kandagatla@linaro.org, linux-arm-msm@vger.kernel.org,
inux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] pinctrl: qcom: Introduce SM4250 LPI pinctrl driver
Date: Sat, 8 Jun 2024 06:12:13 +0800 [thread overview]
Message-ID: <202406080514.8Yq3kzQr-lkp@intel.com> (raw)
In-Reply-To: <20240606130323.138970-3-srinivas.kandagatla@linaro.org>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linusw-pinctrl/devel]
[also build test WARNING on linusw-pinctrl/for-next linus/master v6.10-rc2 next-20240607]
[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/srinivas-kandagatla-linaro-org/dt-bindings-pinctrl-qcom-Add-SM4250-pinctrl/20240606-210728
base: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git devel
patch link: https://lore.kernel.org/r/20240606130323.138970-3-srinivas.kandagatla%40linaro.org
patch subject: [PATCH 2/2] pinctrl: qcom: Introduce SM4250 LPI pinctrl driver
config: sh-randconfig-r131-20240608 (https://download.01.org/0day-ci/archive/20240608/202406080514.8Yq3kzQr-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240608/202406080514.8Yq3kzQr-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/202406080514.8Yq3kzQr-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/pinctrl/qcom/pinctrl-sm4250-lpass-lpi.c:135:9: sparse: sparse: Initializer entry defined twice
drivers/pinctrl/qcom/pinctrl-sm4250-lpass-lpi.c:158:9: sparse: also defined here
vim +135 drivers/pinctrl/qcom/pinctrl-sm4250-lpass-lpi.c
125
126 static const struct lpi_function sm4250_functions[] = {
127 LPI_FUNCTION(dmic01_clk),
128 LPI_FUNCTION(dmic01_data),
129 LPI_FUNCTION(dmic23_clk),
130 LPI_FUNCTION(dmic23_data),
131 LPI_FUNCTION(dmic4_clk),
132 LPI_FUNCTION(dmic4_data),
133 LPI_FUNCTION(ext_mclk0_a),
134 LPI_FUNCTION(ext_mclk0_b),
> 135 LPI_FUNCTION(ext_mclk1_a),
136 LPI_FUNCTION(ext_mclk1_b),
137 LPI_FUNCTION(ext_mclk1_c),
138 LPI_FUNCTION(i2s1_clk),
139 LPI_FUNCTION(i2s1_data),
140 LPI_FUNCTION(i2s1_ws),
141 LPI_FUNCTION(i2s2_clk),
142 LPI_FUNCTION(i2s2_data),
143 LPI_FUNCTION(i2s2_ws),
144 LPI_FUNCTION(i2s3_clk),
145 LPI_FUNCTION(i2s3_data),
146 LPI_FUNCTION(i2s3_ws),
147 LPI_FUNCTION(qua_mi2s_data),
148 LPI_FUNCTION(qua_mi2s_sclk),
149 LPI_FUNCTION(slim_clk),
150 LPI_FUNCTION(slim_data),
151 LPI_FUNCTION(qua_mi2s_ws),
152 LPI_FUNCTION(swr_rx_clk),
153 LPI_FUNCTION(swr_rx_data),
154 LPI_FUNCTION(swr_tx_clk),
155 LPI_FUNCTION(swr_tx_data),
156 LPI_FUNCTION(swr_wsa_clk),
157 LPI_FUNCTION(swr_wsa_data),
158 LPI_FUNCTION(ext_mclk1_a),
159 LPI_FUNCTION(ext_mclk1_a),
160 LPI_FUNCTION(ext_mclk1_a),
161 LPI_FUNCTION(ext_mclk1_a),
162 };
163
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-06-07 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 13:03 [PATCH 0/2] pinctrl: qcom: add sm4250 lpi pinctrl srinivas.kandagatla
2024-06-06 13:03 ` [PATCH 1/2] dt-bindings: pinctrl: qcom: Add SM4250 pinctrl srinivas.kandagatla
2024-06-07 7:36 ` Krzysztof Kozlowski
2024-06-06 13:03 ` [PATCH 2/2] pinctrl: qcom: Introduce SM4250 LPI pinctrl driver srinivas.kandagatla
2024-06-07 7:39 ` Krzysztof Kozlowski
2024-06-07 22:12 ` 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=202406080514.8Yq3kzQr-lkp@intel.com \
--to=lkp@intel.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inux-gpio@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=srinivas.kandagatla@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox