On Fri, 11 Oct 2019 at 13:21, Zhou Wang <wangzhou1@xxxxxxxxxxxxx> wrote: > > To avoid compile error in some platforms, select NEED_SG_DMA_LENGTH in > qm Kconfig. > > Signed-off-by: Zhou Wang <wangzhou1@xxxxxxxxxxxxx> > Reported-by: kbuild test robot <lkp@xxxxxxxxx> > --- > drivers/crypto/hisilicon/Kconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/crypto/hisilicon/Kconfig b/drivers/crypto/hisilicon/Kconfig > index 82fb810d..a71f2bf 100644 > --- a/drivers/crypto/hisilicon/Kconfig > +++ b/drivers/crypto/hisilicon/Kconfig > @@ -18,6 +18,7 @@ config CRYPTO_DEV_HISI_QM > tristate > depends on ARM64 || COMPILE_TEST > depends on PCI && PCI_MSI > + select NEED_SG_DMA_LENGTH > help > HiSilicon accelerator engines use a common queue management > interface. Specific engine driver may use this module. CONFIG_NEED_SG_DMA_LENGTH shouldn't be set by an arbitrary driver - the arch code will set this if needed, and if it doesn't, the additional dma_length field shouldn't be expected to have a meaning. If you are fixing a COMPILE_TEST failure, just add NEED_SG_DMA_LENGTH as a dependency, or drop the COMPILE_TEST altogether (why was that added in the first place?)
