From: Andrew Lunn <andrew@lunn.ch>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: stable@vger.kernel.org, netdev@vger.kernel.org,
Calvin Johnson <calvin.johnson@oss.nxp.com>,
"David S. Miller" <davem@davemloft.net>,
Heiner Kallweit <hkallweit1@gmail.com>,
Ioana Ciornei <ioana.ciornei@nxp.com>,
Jakub Kicinski <kuba@kernel.org>, Rob Herring <robh@kernel.org>,
Russell King <linux@armlinux.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: of_mdio: Checking build dependencies
Date: Thu, 11 Mar 2021 17:26:34 +0100 [thread overview]
Message-ID: <YEpEuoRGh0KoWoGa@lunn.ch> (raw)
In-Reply-To: <a1a749e7-48be-d0ab-8fb5-914daf512ae9@web.de>
On Wed, Mar 10, 2021 at 09:31:07PM +0100, Markus Elfring wrote:
> Hello,
>
> I would like to build the Linux version “5.11.5” for my needs.
> But I stumbled on the following information.
>
> …
> AR drivers/built-in.a
> LD [M] drivers/visorbus/visorbus.o
> GEN .version
> CHK include/generated/compile.h
> error: the following would cause module name conflict:
> drivers/net/mdio/of_mdio.ko
> drivers/of/of_mdio.ko
Hi Markus
Something wrong here. There should not be any of_mdio.ko in
drivers/of. That was the whole point of the patch you referenced, it
moved this file to drivers/net/mdio/. Please check where your
drivers/of/of_mdio.ko comes from. Has there been a bad merge conflict
resolution? Or is it left over from an older build?
Andrew
next parent reply other threads:[~2021-03-11 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a1a749e7-48be-d0ab-8fb5-914daf512ae9@web.de>
2021-03-11 16:26 ` Andrew Lunn [this message]
2021-03-11 17:24 ` of_mdio: Checking build dependencies Masahiro Yamada
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=YEpEuoRGh0KoWoGa@lunn.ch \
--to=andrew@lunn.ch \
--cc=Markus.Elfring@web.de \
--cc=calvin.johnson@oss.nxp.com \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=masahiroy@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh@kernel.org \
--cc=stable@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).