From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [sashal-linux-stable:queue-4.19 154/156] drivers/spi/spi-fsl-dspi.c:1136:34: error: no member named 'ctlr' in 'struct fsl_dspi'
Date: Wed, 08 Jul 2020 10:06:43 +0800 [thread overview]
Message-ID: <202007081040.HGbxtMNg%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3498 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git queue-4.19
head: d122cb882bb9acbdcf6981a6ed413c5ed4f80f6f
commit: 26772c001eb9467848bf5ab5791a93aa5d7907d7 [154/156] spi: spi-fsl-dspi: Fix lockup if device is removed during SPI transfer
config: x86_64-allyesconfig (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 02946de3802d3bc65bc9f2eb9b8d4969b5a7add8)
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
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
git checkout 26772c001eb9467848bf5ab5791a93aa5d7907d7
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
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/spi/spi-fsl-dspi.c:1136:34: error: no member named 'ctlr' in 'struct fsl_dspi'
spi_unregister_controller(dspi->ctlr);
~~~~ ^
drivers/spi/spi-fsl-dspi.c:1140:7: error: use of undeclared identifier 'SPI_MCR_DIS_TXF'
SPI_MCR_DIS_TXF | SPI_MCR_DIS_RXF,
^
drivers/spi/spi-fsl-dspi.c:1140:25: error: use of undeclared identifier 'SPI_MCR_DIS_RXF'
SPI_MCR_DIS_TXF | SPI_MCR_DIS_RXF,
^
drivers/spi/spi-fsl-dspi.c:1141:7: error: use of undeclared identifier 'SPI_MCR_DIS_TXF'
SPI_MCR_DIS_TXF | SPI_MCR_DIS_RXF);
^
drivers/spi/spi-fsl-dspi.c:1141:25: error: use of undeclared identifier 'SPI_MCR_DIS_RXF'
SPI_MCR_DIS_TXF | SPI_MCR_DIS_RXF);
^
drivers/spi/spi-fsl-dspi.c:1144:44: error: use of undeclared identifier 'SPI_MCR_HALT'
regmap_update_bits(dspi->regmap, SPI_MCR, SPI_MCR_HALT, SPI_MCR_HALT);
^
drivers/spi/spi-fsl-dspi.c:1144:58: error: use of undeclared identifier 'SPI_MCR_HALT'
regmap_update_bits(dspi->regmap, SPI_MCR, SPI_MCR_HALT, SPI_MCR_HALT);
^
7 errors generated.
vim +1136 drivers/spi/spi-fsl-dspi.c
1129
1130 static int dspi_remove(struct platform_device *pdev)
1131 {
1132 struct spi_master *master = platform_get_drvdata(pdev);
1133 struct fsl_dspi *dspi = spi_master_get_devdata(master);
1134
1135 /* Disconnect from the SPI framework */
> 1136 spi_unregister_controller(dspi->ctlr);
1137
1138 /* Disable RX and TX */
1139 regmap_update_bits(dspi->regmap, SPI_MCR,
1140 SPI_MCR_DIS_TXF | SPI_MCR_DIS_RXF,
1141 SPI_MCR_DIS_TXF | SPI_MCR_DIS_RXF);
1142
1143 /* Stop Running */
1144 regmap_update_bits(dspi->regmap, SPI_MCR, SPI_MCR_HALT, SPI_MCR_HALT);
1145
1146 dspi_release_dma(dspi);
1147 clk_disable_unprepare(dspi->clk);
1148
1149 return 0;
1150 }
1151
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 65148 bytes --]
reply other threads:[~2020-07-08 2:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202007081040.HGbxtMNg%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.