From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
Cc: Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
Randy Dunlap <rdunlap@infradead.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
broonie@kernel.org,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Jakub Kicinski <kuba@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Vinod Koul <vkoul@kernel.org>,
linux-phy@lists.infradead.org
Subject: Re: [next-20260122] Build failure on IBM Power Server
Date: Fri, 23 Jan 2026 13:07:22 +0200 [thread overview]
Message-ID: <20260123110722.l52ei5bfmx3u7wvl@skbuf> (raw)
In-Reply-To: <2b41debd-9a05-4707-b270-a8fa3dd7768c@kernel.org>
On Fri, Jan 23, 2026 at 11:52:45AM +0100, Christophe Leroy (CS GROUP) wrote:
> Le 23/01/2026 à 11:39, Vladimir Oltean a écrit :
> > On Fri, Jan 23, 2026 at 10:52:49AM +0100, Christophe Leroy (CS GROUP) wrote:
> > > +Vladimir, Maxime, Jakub and netdev
> > >
> > > Le 23/01/2026 à 10:11, Venkat Rao Bagalkote a écrit :
> > > >
> > > > On 23/01/26 1:17 pm, Randy Dunlap wrote:
> > > > >
> > > > > On 1/22/26 8:15 PM, Venkat Rao Bagalkote wrote:
> > > > > > Greetings!!
> > > > > >
> > > > > > IBM CI has reported build failure of 20260122 on IBM Power server.
> > > > > >
> > > > > >
> > > > > > Error:
> > > > > >
> > > > > >
> > > > > > ERROR: modpost: "phy_get_rx_polarity" [drivers/net/phy/
> > > > > > air_en8811h.ko] undefined!
> > > > > > ERROR: modpost: "phy_get_tx_polarity" [drivers/net/phy/
> > > > > > air_en8811h.ko] undefined!
> > > > > > make[2]: *** [scripts/Makefile.modpost:147: Module.symvers] Error 1
> > > > > > make[1]: *** [/home/upstreamci/linux/Makefile:2040: modpost] Error 2
> > > > > > make: *** [Makefile:248: __sub-make] Error 2
> > >
> > > Thanks for the config file.
> > >
> > > The probleme is because allthough CONFIG_PHY_COMMON_PROPS is selected,
> > > drivers/phy/phy-common-props.o is not built because CONFIG_GENERIC_PHY
> > > is not selected.
> > >
> > > Likely comes from commit 66d8a334b57e ("net: phy: air_en8811h: deprecate
> > > "airoha,pnswap-rx" and "airoha,pnswap-tx"")
> > >
> > > Christophe
> >
> > The intention was for drivers/phy/phy-common-props.o to be
> > buildable/usable without CONFIG_GENERIC_PHY.
> >
> > Does this help?
>
> Yes it fixes the build for me.
>
> Christophe
Patch sent:
https://lore.kernel.org/linux-phy/20260123110600.3118561-1-vladimir.oltean@nxp.com/
prev parent reply other threads:[~2026-01-23 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43ea0202-891d-4582-980b-5cb557b41114@linux.ibm.com>
[not found] ` <f07d721f-ac80-4421-86a3-1f7f76ea8e6c@infradead.org>
[not found] ` <136ae3bf-b1a3-4ee8-a7ea-dfc90e7b4baf@linux.ibm.com>
2026-01-23 9:52 ` [next-20260122] Build failure on IBM Power Server Christophe Leroy (CS GROUP)
2026-01-23 10:39 ` Vladimir Oltean
2026-01-23 10:52 ` Christophe Leroy (CS GROUP)
2026-01-23 11:07 ` Vladimir Oltean [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=20260123110722.l52ei5bfmx3u7wvl@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=broonie@kernel.org \
--cc=chleroy@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=venkat88@linux.ibm.com \
--cc=vkoul@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