linux-kernel - Re: [PATCH 2/2] pinctrl: qcom: Introduce SM4250 LPI pinctrl driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Sat, 8 Jun 2024 06:12:13 +0800
From: kernel test robot <lkp@...el.com>
To: srinivas.kandagatla@...aro.org, andersson@...nel.org,
	linus.walleij@...aro.org
Cc: oe-kbuild-all@...ts.linux.dev, robh@...nel.org, krzk+dt@...nel.org,
	conor+dt@...nel.org, srinivas.kandagatla@...aro.org,
	linux-arm-msm@...r.kernel.org, inux-gpio@...r.kernel.org,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] pinctrl: qcom: Introduce SM4250 LPI pinctrl driver

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@...el.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