From: Ioana Ciornei <ioana.ciornei@nxp.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jose Abreu <Jose.Abreu@synopsys.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Andrew Lunn <andrew@lunn.ch>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for Oct 15 (drivers/net/pcs/pcs-xpcs.o)
Date: Thu, 15 Oct 2020 18:06:08 +0000 [thread overview]
Message-ID: <20201015180607.xtackyvta7nsiwzh@skbuf> (raw)
In-Reply-To: <3418cac1-eff7-d06a-6ba7-9877f0f266e9@infradead.org>
On Thu, Oct 15, 2020 at 10:48:56AM -0700, Randy Dunlap wrote:
> On 10/15/20 10:02 AM, Ioana Ciornei wrote:
> > On Thu, Oct 15, 2020 at 03:06:42PM +0000, Jose Abreu wrote:
> >> From: Randy Dunlap <rdunlap@infradead.org>
> >> Date: Oct/15/2020, 15:45:57 (UTC+00:00)
> >>
> >>> On 10/15/20 12:28 AM, Stephen Rothwell wrote:
> >>>> Hi all,
> >>>>
> >>>> Since the merge window is open, please do not add any v5.11 material to
> >>>> your linux-next included branches until after v5.10-rc1 has been released.
> >>>>
> >>>> News: there will be no linux-next releases next Monday or Tuesday.
> >>>>
> >>>> Changes since 20201013:
> >>>>
> >>>
> >>> on i386:
> >>>
> >>> ld: drivers/net/pcs/pcs-xpcs.o: in function `xpcs_read':
> >>> pcs-xpcs.c:(.text+0x29): undefined reference to `mdiobus_read'
> >>> ld: drivers/net/pcs/pcs-xpcs.o: in function `xpcs_soft_reset.constprop.7':
> >>> pcs-xpcs.c:(.text+0x80): undefined reference to `mdiobus_write'
> >>> ld: drivers/net/pcs/pcs-xpcs.o: in function `xpcs_config_aneg':
> >>> pcs-xpcs.c:(.text+0x318): undefined reference to `mdiobus_write'
> >>> ld: pcs-xpcs.c:(.text+0x38e): undefined reference to `mdiobus_write'
> >>> ld: pcs-xpcs.c:(.text+0x3eb): undefined reference to `mdiobus_write'
> >>> ld: pcs-xpcs.c:(.text+0x437): undefined reference to `mdiobus_write'
> >>> ld: drivers/net/pcs/pcs-xpcs.o:pcs-xpcs.c:(.text+0xb1e): more undefined references to `mdiobus_write' follow
> >>>
> >>>
> >
> > I think this stems from the fact that PHYLIB is configured as a module
> > which leads to MDIO_BUS being a module as well while the XPCS is still
> > built-in. What should happen in this configuration is that PCS_XPCS
> > should be forced to build as module. However, that select only acts in
> > the opposite way so we should turn it into a depends.
> >
> > Is the below patch acceptable? If it is, I can submit it properly.
>
> Hi,
> Did you copy-paste this patch? It contains spaces instead of tabs
> so it doesn't apply cleanly/easily, but I managed to apply and test it, so
>
Yes, it was a quick copy-paste. Sorry for the trouble.
> Acked-by: Randy Dunlap <rdunlap@infradead.org> # build-tested
>
Thanks.
Ioana
prev parent reply other threads:[~2020-10-15 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 7:28 linux-next: Tree for Oct 15 Stephen Rothwell
2020-10-15 14:45 ` linux-next: Tree for Oct 15 (drivers/net/pcs/pcs-xpcs.o) Randy Dunlap
2020-10-15 15:06 ` Jose Abreu
2020-10-15 17:02 ` Ioana Ciornei
2020-10-15 17:48 ` Randy Dunlap
2020-10-15 18:06 ` Ioana Ciornei [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=20201015180607.xtackyvta7nsiwzh@skbuf \
--to=ioana.ciornei@nxp.com \
--cc=Jose.Abreu@synopsys.com \
--cc=andrew@lunn.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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