From: kernel test robot <lkp@intel.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: ERROR: modpost: "__delay" [drivers/net/mdio/mdio-cavium.ko] undefined!
Date: Sat, 28 Dec 2024 21:35:11 +0800 [thread overview]
Message-ID: <202412282326.0DSE4HbR-lkp@intel.com> (raw)
Hi Andrew,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: fd0584d220fe285dc45be43eede55df89ad6a3d9
commit: a9770eac511ad82390b9f4a3c1728e078c387ac7 net: mdio: Move MDIO drivers into a new subdirectory
date: 4 years, 4 months ago
config: sh-randconfig-001-20241212 (https://download.01.org/0day-ci/archive/20241228/202412282326.0DSE4HbR-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241228/202412282326.0DSE4HbR-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/202412282326.0DSE4HbR-lkp@intel.com/
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "__delay" [drivers/net/mdio/mdio-cavium.ko] undefined!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-12-28 13:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 13:35 kernel test robot [this message]
2024-12-28 13:50 ` ERROR: modpost: "__delay" [drivers/net/mdio/mdio-cavium.ko] undefined! Geert Uytterhoeven
2024-12-28 13:55 ` Geert Uytterhoeven
2024-12-29 2:23 ` Philip Li
-- strict thread matches above, loose matches on Subject: below --
2024-07-26 0:38 kernel test robot
2024-07-26 7:26 ` Geert Uytterhoeven
2024-07-11 17:34 kernel test robot
2024-03-23 20:39 kernel test robot
2022-07-16 6:59 kernel test robot
2021-07-24 23:11 kernel test robot
2021-07-11 0:49 kernel test robot
2021-05-29 23:25 kernel test robot
2021-05-31 0:05 ` Randy Dunlap
2021-05-31 1:13 ` Randy Dunlap
2021-05-31 7:36 ` Geert Uytterhoeven
2021-05-31 14:34 ` Randy Dunlap
2021-05-31 14:46 ` Andrew Lunn
2021-05-31 15:09 ` Geert Uytterhoeven
2021-05-31 7:29 ` Geert Uytterhoeven
2021-05-31 7:32 ` Geert Uytterhoeven
2021-05-31 15:12 ` Randy Dunlap
2021-05-31 15:45 ` Geert Uytterhoeven
2021-06-02 3:52 ` Randy Dunlap
2021-05-19 23:52 kernel test robot
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=202412282326.0DSE4HbR-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew@lunn.ch \
--cc=linux-kernel@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