On 1/9/21 11:48 AM, Andrew Lunn wrote:
> On Sat, Jan 09, 2021 at 10:17:38AM +0100, Zhi Han wrote:
>> Thanks a lot for the .config file.
>> I also tested it, with mdio-bus.o in the Makefile, glad to got that there is
>> no problem of that, although I don't know the reason/trick yet.
>
> I'm not 100
On Sat, Jan 09, 2021 at 10:17:38AM +0100, Zhi Han wrote:
> Thanks a lot for the .config file.
> I also tested it, with mdio-bus.o in the Makefile, glad to got that there is
> no problem of that, although I don't know the reason/trick yet.
I'm not 100% sure, but i think:
obj-$(CONFIG_MDIO_DEVICE)
Thanks a lot for the .config file.
I also tested it, with mdio-bus.o in the Makefile, glad to got that there is
no problem of that, although I don't know the reason/trick yet.
On Wed, Jan 06, 2021 at 04:13:56PM -0800, Florian Fainelli wrote:
> The change was done on purpose, and your patch does no
On 1/6/21 2:17 AM, Zhi Han wrote:
> It should be a typing error ('-' instead of '_'), as no mdio-bus.c but
> just mdio_bus.c exists.
>
> Just find it when inspecting these code. Tried to compile to test, but
> failed to construct an applicable .config file for that. Maybe someone
> can do that mor
On Wed, 6 Jan 2021 11:17:12 +0100 Zhi Han wrote:
> It should be a typing error ('-' instead of '_'), as no mdio-bus.c but
> just mdio_bus.c exists.
>
> Just find it when inspecting these code. Tried to compile to test, but
> failed to construct an applicable .config file for that. Maybe someone
>
It should be a typing error ('-' instead of '_'), as no mdio-bus.c but
just mdio_bus.c exists.
Just find it when inspecting these code. Tried to compile to test, but
failed to construct an applicable .config file for that. Maybe someone
can do that more skillfully, glad to know how.
Signed-off-by
