On Tue, 1 Dec 2020 20:41:21 -0800 Randy Dunlap wrote:
> On 12/1/20 8:01 PM, kernel test robot wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git master
> > head:   2867e1eac61016f59b3d730e3f7aa488e186e917
> > commit: 14483cbf040fcb38113497161088a1ce8ce5d713 [1/3] net: broadcom CNIC: 
> > requires MMU
> > config: microblaze-randconfig-r011-20201201 (attached as .config)
> > compiler: microblaze-linux-gcc (GCC) 9.3.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/davem/net.git/commit/?id=14483cbf040fcb38113497161088a1ce8ce5d713
> >         git remote add net 
> > https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git
> >         git fetch --no-tags net master
> >         git checkout 14483cbf040fcb38113497161088a1ce8ce5d713
> >         # save the attached .config to linux build tree
> >         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross 
> > ARCH=microblaze 
> > 
> > If you fix the issue, kindly add following tag as appropriate
> > Reported-by: kernel test robot <l...@intel.com>
> > 
> > All errors (new ones prefixed by >>, old ones prefixed by <<):
> >   
> >>> ERROR: modpost: "__uio_register_device" 
> >>> [drivers/net/ethernet/broadcom/cnic.ko] undefined!
> >>> ERROR: modpost: "uio_unregister_device" 
> >>> [drivers/net/ethernet/broadcom/cnic.ko] undefined!
> >>> ERROR: modpost: "uio_event_notify" 
> >>> [drivers/net/ethernet/broadcom/cnic.ko] undefined!  
> 
> Jakub,
> 
> This happens due to CONFIG_SCSI_BNX2_ISCSI=m, which selects CNIC
> when it shouldn't.
> 
> Martin Petersen has already merged the SCSI patch for this (for 5.11,
> sadly):
> 
> https://lore.kernel.org/lkml/20201129070916.3919-1-rdun...@infradead.org/
> 
> 
> Maybe I should have sent them to one or both of you as a 2-patch series (?).
> 
> What should we do next?

Martin is it an option to drop the patch from scsi-staging and put it
in the queue for 5.10 (yours or ours)?

Reply via email to