From: "Arnd Bergmann" <arnd@arndb•de>
To: "Naresh Kamboju" <naresh.kamboju@linaro•org>,
Netdev <netdev@vger•kernel.org>,
linux-next <linux-next@vger•kernel.org>,
"Linux ARM" <linux-arm-kernel@lists•infradead.org>,
lkft-triage@lists•linaro.org, llvm@lists•linux.dev
Cc: "Russell King" <linux@armlinux•org.uk>,
"David S . Miller" <davem@davemloft•net>,
"Ard Biesheuvel" <ardb@kernel•org>,
"Anders Roxell" <anders.roxell@linaro•org>,
"Eric Dumazet" <edumazet@google•com>,
"Paolo Abeni" <pabeni@redhat•com>,
"Jakub Kicinski" <kuba@kernel•org>
Subject: Re: next: arm: drivers/net/phy/phy_device.o: in function `phy_probe': drivers/net/phy/phy_device.c:3053: undefined reference to
Date: Thu, 20 Apr 2023 14:21:10 +0200 [thread overview]
Message-ID: <a5ed97f2-b3f8-454b-a63a-16e7153003a6@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYuMEEzTUyF-pCVuZYd+BU53_8MRyXoOmbYEo1O1v=9teg@mail.gmail.com>
On Thu, Apr 20, 2023, at 12:51, Naresh Kamboju wrote:
> [ Please ignore this email if it is already reported ]
>
> Following build failures noticed on Linux next-20230419.
>
> Regressions found on arm:
> - build/clang-16-omap2plus_defconfig
> - build/clang-16-davinci_all_defconfig
> - build/gcc-8-davinci_all_defconfig
> - build/clang-nightly-omap2plus_defconfig
> - build/gcc-12-omap2plus_defconfig
> - build/gcc-12-davinci_all_defconfig
> - build/clang-nightly-davinci_all_defconfig
> - build/gcc-8-omap2plus_defconfig
>
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro•org>
>
> Build log:
> ------------
>
> arm-linux-gnueabihf-ld: drivers/net/phy/phy_device.o: in function `phy_probe':
> drivers/net/phy/phy_device.c:3053: undefined reference to
> `devm_led_classdev_register_ext'
I sent this patch now:
https://lore.kernel.org/all/20230420084624.3005701-1-arnd@kernel.org/
Arnd
prev parent reply other threads:[~2023-04-20 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 10:51 next: arm: drivers/net/phy/phy_device.o: in function `phy_probe': drivers/net/phy/phy_device.c:3053: undefined reference to Naresh Kamboju
2023-04-20 12:21 ` Arnd Bergmann [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=a5ed97f2-b3f8-454b-a63a-16e7153003a6@app.fastmail.com \
--to=arnd@arndb$(echo .)de \
--cc=anders.roxell@linaro$(echo .)org \
--cc=ardb@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=lkft-triage@lists$(echo .)linaro.org \
--cc=llvm@lists$(echo .)linux.dev \
--cc=naresh.kamboju@linaro$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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