From: Philip Li <philip.li@intel.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: kernel test robot <lkp@intel.com>, Andrew Lunn <andrew@lunn.ch>,
<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<linux-mips@vger.kernel.org>
Subject: Re: ERROR: modpost: "__delay" [drivers/net/mdio/mdio-cavium.ko] undefined!
Date: Sun, 29 Dec 2024 10:23:29 +0800 [thread overview]
Message-ID: <Z3CyoSB2hTDyGz7R@rli9-mobl> (raw)
In-Reply-To: <CAMuHMdVHGz=0d_bGOu7RtF7-ssgnNmHk=MwEbTK77=+UgKGmYA@mail.gmail.com>
On Sat, Dec 28, 2024 at 02:55:02PM +0100, Geert Uytterhoeven wrote:
> On Sat, Dec 28, 2024 at 2:50 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > Hi Kernel Test Robot,
> >
> > On Sat, Dec 28, 2024 at 2:36 PM kernel test robot <lkp@intel.com> wrote:
> > > 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!
> >
> > The real issue was introduced in commit 1eefee901fca0208
> > ("phy: mdio-octeon: Refactor into two files/modules").
>
> Silly me: commit 2fd46f47be0f96be
> ("netdev: mdio-octeon.c: Convert to use device tree.").
> But even before that, the driver used a different non-portable construct.
>
> > Drivers must not use __delay() directly, as that is non-portable, and
> > doesn't work in the presence of cpufreq.
>
> And looking at
> https://lore.kernel.org/all/202412282326.0DSE4HbR-lkp@intel.com
> all of this has been said before...
Sorry Geert about the false report that costs your effort to check, we should
avoid reporting against this commit after that discussion. I will fix it asap.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
prev parent reply other threads:[~2024-12-29 2:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202412282326.0DSE4HbR-lkp@intel.com>
[not found] ` <CAMuHMdUTtdQxyTUSd_NBiPvL6irb8p_2+=hk5PjUrXC4J=VrbA@mail.gmail.com>
2024-12-28 13:55 ` ERROR: modpost: "__delay" [drivers/net/mdio/mdio-cavium.ko] undefined! Geert Uytterhoeven
2024-12-29 2:23 ` Philip Li [this message]
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=Z3CyoSB2hTDyGz7R@rli9-mobl \
--to=philip.li@intel.com \
--cc=andrew@lunn.ch \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lkp@intel.com \
--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