Re: [broonie-ci:20220318_rf_asoc_add_a_driver_for_the_cirrus_logic_cs35l45_smart_amplifier 29/29] sound/soc/codecs/cs35l45-spi.c:66:27: error: initialization of 'void (*)(struct spi_device *)' from incompatible pointer type 'int (*)(struct spi_device *)'

[Richard Fitzgerald]

On 06/04/2022 06:04, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/ci.git 20220318_rf_asoc_add_a_driver_for_the_cirrus_logic_cs35l45_smart_amplifier
> head:   22d0ed9e232c66cf1d388c39fafac77c0872ae79
> commit: 22d0ed9e232c66cf1d388c39fafac77c0872ae79 [29/29] ASoC: cs35l45: Add driver for Cirrus Logic CS35L45 Smart Amp
> config: riscv-allmodconfig (https://download.01.org/0day-ci/archive/20220406/202204061233.zD5PMrQA-lkp@xxxxxxxxx/config)
> compiler: riscv64-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://git.kernel.org/pub/scm/linux/kernel/git/broonie/ci.git/commit/?id=22d0ed9e232c66cf1d388c39fafac77c0872ae79
>          git remote add broonie-ci https://git.kernel.org/pub/scm/linux/kernel/git/broonie/ci.git
>          git fetch --no-tags broonie-ci 20220318_rf_asoc_add_a_driver_for_the_cirrus_logic_cs35l45_smart_amplifier
>          git checkout 22d0ed9e232c66cf1d388c39fafac77c0872ae79
>          # save the config file to linux build tree
>          mkdir build_dir
>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=riscv SHELL=/bin/bash sound/soc/
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@xxxxxxxxx>
>
> All errors (new ones prefixed by >>):
>
> > > sound/soc/codecs/cs35l45-spi.c:66:27: error: initialization of 'void (*)(struct spi_device *)' from incompatible pointer type 'int (*)(struct spi_device *)' [-Werror=incompatible-pointer-types]
>        66 |         .remove         = cs35l45_spi_remove,
>           |                           ^~~~~~~~~~~~~~~~~~

This is fixed in V2 of the patch.