From: Randy Dunlap <rdunlap@infradead.org>
To: Simon Horman <simon.horman@corigine.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bryan Whitehead <bryan.whitehead@microchip.com>,
Network Development <netdev@vger.kernel.org>,
UNGLinuxDriver@microchip.com,
Pavithra Sathyanarayanan <Pavithra.Sathyanarayanan@microchip.com>
Subject: Re: linux-next: Tree for Jul 4 (drivers/net/ethernet/microchip/lan743x_main.c)
Date: Thu, 6 Jul 2023 16:29:26 -0700 [thread overview]
Message-ID: <e2be9c20-4e0c-7880-ba0d-11b8f2c5404c@infradead.org> (raw)
In-Reply-To: <ZKc2DLIroSNi4tgs@corigine.com>
Hi Simon,
On 7/6/23 14:45, Simon Horman wrote:
> + Pavithra Sathyanarayanan
>
> On Tue, Jul 04, 2023 at 03:25:31AM -0700, Randy Dunlap wrote:
>>
>>
>> On 7/3/23 20:43, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Please do *not* add any v6.6 related stuff to your linux-next included
>>> branches until after v6.5-rc1 has been released.
>>>
>>> Changes since 20230703:
>>>
>>
>> on s390:
>>
>> s390-linux-ld: drivers/net/ethernet/microchip/lan743x_main.o: in function `lan743x_phy_open':
>> drivers/net/ethernet/microchip/lan743x_main.c:1514: undefined reference to `fixed_phy_register'
>>
>>
>> Full randconfig file is attached.
>
> Thanks for the config.
>
> I bisected this problem and it appears to be introduced by:
>
> 624864fbff92 ("net: lan743x: add fixed phy support for LAN7431 device")
>
> I wonder if the following change in dependencies is an appropriate fix for
> this problem.
Yes, that change fixes the build error. Thanks.
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org> # build-tested
>
> diff --git a/drivers/net/ethernet/microchip/Kconfig b/drivers/net/ethernet/microchip/Kconfig
> index 24c994baad13..329e374b9539 100644
> --- a/drivers/net/ethernet/microchip/Kconfig
> +++ b/drivers/net/ethernet/microchip/Kconfig
> @@ -46,7 +46,7 @@ config LAN743X
> tristate "LAN743x support"
> depends on PCI
> depends on PTP_1588_CLOCK_OPTIONAL
> - select PHYLIB
> + select FIXED_PHY
> select CRC16
> select CRC32
> help
>
--
~Randy
prev parent reply other threads:[~2023-07-06 23:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 3:43 linux-next: Tree for Jul 4 Stephen Rothwell
2023-07-04 10:25 ` linux-next: Tree for Jul 4 (drivers/net/ethernet/microchip/lan743x_main.c) Randy Dunlap
2023-07-06 21:45 ` Simon Horman
2023-07-06 23:29 ` Randy Dunlap [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=e2be9c20-4e0c-7880-ba0d-11b8f2c5404c@infradead.org \
--to=rdunlap@infradead.org \
--cc=Pavithra.Sathyanarayanan@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=bryan.whitehead@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=simon.horman@corigine.com \
/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
all inboxes | Powered by JetHome®