Re: [PATCH 0/3] resolve module name conflict for asix PHY and USB modules

2019-05-17 Thread Michael Schmitz
Thanks Andrew, makes perfect sense - patch resent. Cheers, Michael Am 18.05.2019 um 09:20 schrieb Andrew Lunn: On Sat, May 18, 2019 at 08:25:15AM +1200, Michael Schmitz wrote: Haven't heard back in a while, so here goes: Commit 31dd83b96641 ("net-next: phy: new Asix Electronics PHY

Re: [PATCH 0/3] resolve module name conflict for asix PHY and USB modules

2019-05-17 Thread Andrew Lunn
On Sat, May 18, 2019 at 08:25:15AM +1200, Michael Schmitz wrote: > Haven't heard back in a while, so here goes: > > Commit 31dd83b96641 ("net-next: phy: new Asix Electronics PHY driver") > introduced a new PHY driver drivers/net/phy/asix.c that causes a module > name conflict with a pre-existitin

[PATCH 0/3] resolve module name conflict for asix PHY and USB modules

2019-05-17 Thread Michael Schmitz
Haven't heard back in a while, so here goes: Commit 31dd83b96641 ("net-next: phy: new Asix Electronics PHY driver") introduced a new PHY driver drivers/net/phy/asix.c that causes a module name conflict with a pre-existiting driver (drivers/net/usb/asix.c). The PHY driver is used by the X-Surf 1