Re: [PATCH] net: Always descend into dsa/

2019-05-14 Thread David Miller
From: Florian Fainelli Date: Mon, 13 May 2019 14:06:24 -0700 > Jiri reported that with a kernel built with CONFIG_FIXED_PHY=y, > CONFIG_NET_DSA=m and CONFIG_NET_DSA_LOOP=m, we would not get to a > functional state where the mock-up driver is registered. Turns out that > we are not descending into

Re: [PATCH] net: Always descend into dsa/

2019-05-14 Thread Jiri Pirko
Mon, May 13, 2019 at 11:06:24PM CEST, f.faine...@gmail.com wrote: >Jiri reported that with a kernel built with CONFIG_FIXED_PHY=y, >CONFIG_NET_DSA=m and CONFIG_NET_DSA_LOOP=m, we would not get to a >functional state where the mock-up driver is registered. Turns out that >we are not descending into

Re: [PATCH] net: Always descend into dsa/

2019-05-13 Thread Vivien Didelot
On Mon, 13 May 2019 14:06:24 -0700, Florian Fainelli wrote: > Jiri reported that with a kernel built with CONFIG_FIXED_PHY=y, > CONFIG_NET_DSA=m and CONFIG_NET_DSA_LOOP=m, we would not get to a > functional state where the mock-up driver is registered. Turns out that > we are not descending into

[PATCH] net: Always descend into dsa/

2019-05-13 Thread Florian Fainelli
Jiri reported that with a kernel built with CONFIG_FIXED_PHY=y, CONFIG_NET_DSA=m and CONFIG_NET_DSA_LOOP=m, we would not get to a functional state where the mock-up driver is registered. Turns out that we are not descending into drivers/net/dsa/ unconditionally, and we won't be able to link-in dsa_