From: Randy Dunlap <rdunlap@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, netdev@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [net:master 1/3] ERROR: modpost: "__uio_register_device" undefined!
Date: Tue, 1 Dec 2020 20:41:21 -0800 [thread overview]
Message-ID: <8875896f-81a7-cbda-3b6e-97b5b22383c3@infradead.org> (raw)
In-Reply-To: <202012021229.9PwxJvFJ-lkp@intel.com>
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 <lkp@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-rdunlap@infradead.org/
Maybe I should have sent them to one or both of you as a 2-patch series (?).
What should we do next?
Sorry about this. Thanks.
--
~Randy
next prev parent reply other threads:[~2020-12-02 4:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 4:01 [net:master 1/3] ERROR: modpost: "__uio_register_device" undefined! kernel test robot
2020-12-02 4:41 ` Randy Dunlap [this message]
2020-12-02 17:46 ` Jakub Kicinski
2020-12-02 17:52 ` Martin K. Petersen
2020-12-02 17:56 ` Jakub Kicinski
2020-12-02 18:02 ` Martin K. Petersen
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=8875896f-81a7-cbda-3b6e-97b5b22383c3@infradead.org \
--to=rdunlap@infradead.org \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=lkp@intel.com \
--cc=martin.petersen@oracle.com \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).