Re: linux-next: build failure after merge of the phy-next tree

Vinod Koul
2021-12-24T04:37:31Z

On 24-12-21, 14:03, Stephen Rothwell wrote:
> Hi all,
>
> After merging the phy-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/phy/phy-can-transceiver.c: In function 'can_transceiver_phy_power_on':
> drivers/phy/phy-can-transceiver.c:35:9: error: implicit declaration of function 'mux_state_select'; did you mean 'mux_control_select'? [-Werror=implicit-function-declaration]
> 35 | ret = mux_state_select(can_transceiver_phy->mux_state);
> | ^~~~~~~~~~~~~~~~
> | mux_control_select
> drivers/phy/phy-can-transceiver.c: In function 'can_transceiver_phy_power_off':
> drivers/phy/phy-can-transceiver.c:59:3: error: implicit declaration of function 'mux_state_deselect'; did you mean 'mux_control_deselect'? [-Werror=implicit-function-declaration]
> 59 | mux_state_deselect(can_transceiver_phy->mux_state);
> | ^~~~~~~~~~~~~~~~~~
> | mux_control_deselect
> drivers/phy/phy-can-transceiver.c: In function 'can_transceiver_phy_probe':
> drivers/phy/phy-can-transceiver.c:113:15: error: implicit declaration of function 'devm_mux_state_get'; did you mean 'devm_mux_control_get'? [-Werror=implicit-function-declaration]
> 113 | mux_state = devm_mux_state_get(dev, NULL);
> | ^~~~~~~~~~~~~~~~~~
> | devm_mux_control_get
> drivers/phy/phy-can-transceiver.c:113:13: error: assignment to 'struct mux_state *' from 'int' makes pointer from integer without a cast [-Werror=int-conversion]
> 113 | mux_state = devm_mux_state_get(dev, NULL);
> | ^
> cc1: all warnings being treated as errors
>
> Caused by commit
>
> 1e68cd3ff73e ("phy: phy-can-transceiver: Add support for setting mux")
>
> I have used the phy-next tree from next-20211223 for today.

Thanks for letting me know. I have dropped the offending commit

--
~Vinod