Re: [PATCH 5.10 134/717] spi: dw: fix build error by selecting MULTIPLEXER
On Thu, Dec 31, 2020 at 12:10:34PM +0300, Serge Semin wrote: > On Thu, Dec 31, 2020 at 09:51:21AM +0100, Greg Kroah-Hartman wrote: > > On Thu, Dec 31, 2020 at 11:49:56AM +0300, Serge Semin wrote: > > > Hello Greg, > > > The next patch has been created to supersede the one you've applied: > > > https://lore.kernel.org/linux-spi/20201127144612.4204-1-sergey.se...@baikalelectronics.ru/ > > > Mark has already merged it in his repo. > > > > > Ok, so should that one be queued up as well? Let us know the git commit > > id of it when it reaches Linus's kernel and we will be glad to take it. > > I believe it is already there: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7218838109fef61cdec988ff728e902d434c9cc5 > Yeah, it's better to queue that patch up too, otherwise the build > error will be indeed fixed by the commit you've merged in, but the > probe procedure will still always fail. Ok, now queued up, thanks for letting us know. greg k-h
Re: [PATCH 5.10 134/717] spi: dw: fix build error by selecting MULTIPLEXER
On Thu, Dec 31, 2020 at 09:51:21AM +0100, Greg Kroah-Hartman wrote: > On Thu, Dec 31, 2020 at 11:49:56AM +0300, Serge Semin wrote: > > Hello Greg, > > The next patch has been created to supersede the one you've applied: > > https://lore.kernel.org/linux-spi/20201127144612.4204-1-sergey.se...@baikalelectronics.ru/ > > Mark has already merged it in his repo. > > Ok, so should that one be queued up as well? Let us know the git commit > id of it when it reaches Linus's kernel and we will be glad to take it. I believe it is already there: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7218838109fef61cdec988ff728e902d434c9cc5 Yeah, it's better to queue that patch up too, otherwise the build error will be indeed fixed by the commit you've merged in, but the probe procedure will still always fail. -Sergey > > thanks, > > greg k-h
Re: [PATCH 5.10 134/717] spi: dw: fix build error by selecting MULTIPLEXER
On Thu, Dec 31, 2020 at 11:49:56AM +0300, Serge Semin wrote: > Hello Greg, > The next patch has been created to supersede the one you've applied: > https://lore.kernel.org/linux-spi/20201127144612.4204-1-sergey.se...@baikalelectronics.ru/ > Mark has already merged it in his repo. Ok, so should that one be queued up as well? Let us know the git commit id of it when it reaches Linus's kernel and we will be glad to take it. thanks, greg k-h
Re: [PATCH 5.10 134/717] spi: dw: fix build error by selecting MULTIPLEXER
Hello Greg, The next patch has been created to supersede the one you've applied: https://lore.kernel.org/linux-spi/20201127144612.4204-1-sergey.se...@baikalelectronics.ru/ Mark has already merged it in his repo. -Sergey On Mon, Dec 28, 2020 at 01:42:12PM +0100, Greg Kroah-Hartman wrote: > From: Randy Dunlap > > [ Upstream commit 1241f0787578136ab58f49adc52f2dcd2bbc4bf2 ] > > Fix build error for spi-dw-bt1.o by selecting MULTIPLEXER. > > hppa-linux-ld: drivers/spi/spi-dw-bt1.o: in function `dw_spi_bt1_sys_init': > (.text+0x1ac): undefined reference to `devm_mux_control_get' > > Fixes: abf00907538e ("spi: dw: Add Baikal-T1 SPI Controller glue driver") > Reported-by: kernel test robot > Signed-off-by: Randy Dunlap > Cc: Serge Semin > Cc: Ramil Zaripov > Cc: Mark Brown > Cc: linux-...@vger.kernel.org > Acked-by: Serge Semin > Link: https://lore.kernel.org/r/20201116040721.8001-1-rdun...@infradead.org > Signed-off-by: Mark Brown > Signed-off-by: Sasha Levin > --- > drivers/spi/Kconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig > index 5cff60de8e834..3fd16b7f61507 100644 > --- a/drivers/spi/Kconfig > +++ b/drivers/spi/Kconfig > @@ -255,6 +255,7 @@ config SPI_DW_MMIO > config SPI_DW_BT1 > tristate "Baikal-T1 SPI driver for DW SPI core" > depends on MIPS_BAIKAL_T1 || COMPILE_TEST > + select MULTIPLEXER > help > Baikal-T1 SoC is equipped with three DW APB SSI-based MMIO SPI > controllers. Two of them are pretty much normal: with IRQ, DMA, > -- > 2.27.0 > > >