From: kernel test robot <lkp@intel.com>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>
Subject: [net-next:main 35/51] drivers/net/ethernet/cadence/macb_main.c:5710:19: error: 'at91_default_usrio' undeclared here (not in a function)
Date: Mon, 30 Mar 2026 23:21:54 +0800 [thread overview]
Message-ID: <202603302354.afJpLbxZ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git main
head: cf0d9080c6f795bc6be08babbffa29b62c06e9b0
commit: a17871778ee28e4df054521e966e9f37c61f541b [35/51] net: macb: rename macb_default_usrio to at91_default_usrio as not all platforms have mii mode control in usrio
config: i386-randconfig-016-20260330 (https://download.01.org/0day-ci/archive/20260330/202603302354.afJpLbxZ-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260330/202603302354.afJpLbxZ-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202603302354.afJpLbxZ-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/net/ethernet/cadence/macb_main.c:5710:19: error: 'at91_default_usrio' undeclared here (not in a function)
5710 | .usrio = &at91_default_usrio,
| ^~~~~~~~~~~~~~~~~~
vim +/at91_default_usrio +5710 drivers/net/ethernet/cadence/macb_main.c
5704
5705 static const struct macb_config default_gem_config = {
5706 .caps = MACB_CAPS_GIGABIT_MODE_AVAILABLE |
5707 MACB_CAPS_JUMBO |
5708 MACB_CAPS_GEM_HAS_PTP,
5709 .dma_burst_length = 16,
> 5710 .usrio = &at91_default_usrio,
5711 .jumbo_max_len = 10240,
5712 };
5713
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-30 15:22 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=202603302354.afJpLbxZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=conor.dooley@microchip.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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