[PATCH usb-next v1] usb: core: phy: fix return value of usb_phy_roothub_exit()

2018-03-24 Thread Martin Blumenstingl
usb_phy_roothub_exit() should return the error code from the phy_exit() call if exiting the PHY failed. However, since a wrong variable is used usb_phy_roothub_exit() currently always returns 0, even if one of the phy_exit calls returned an error. Fix this by assigning the error code from phy_exit(

Re: [PATCH usb-next v1] usb: core: phy: fix return value of usb_phy_roothub_exit()

2018-03-25 Thread Chunfeng Yun
On Sat, 2018-03-24 at 14:56 +0100, Martin Blumenstingl wrote: > usb_phy_roothub_exit() should return the error code from the phy_exit() > call if exiting the PHY failed. > However, since a wrong variable is used usb_phy_roothub_exit() currently > always returns 0, even if one of the phy_exit calls

Re: [PATCH usb-next v1] usb: core: phy: fix return value of usb_phy_roothub_exit()

2018-03-26 Thread Martin Blumenstingl
Hi Chunfeng, On Mon, Mar 26, 2018 at 5:43 AM, Chunfeng Yun wrote: > On Sat, 2018-03-24 at 14:56 +0100, Martin Blumenstingl wrote: >> usb_phy_roothub_exit() should return the error code from the phy_exit() >> call if exiting the PHY failed. >> However, since a wrong variable is used usb_phy_roothu

Re: [PATCH usb-next v1] usb: core: phy: fix return value of usb_phy_roothub_exit()

2018-03-26 Thread Chunfeng Yun
Hi, On Mon, 2018-03-26 at 22:12 +0200, Martin Blumenstingl wrote: > Hi Chunfeng, > > On Mon, Mar 26, 2018 at 5:43 AM, Chunfeng Yun > wrote: > > On Sat, 2018-03-24 at 14:56 +0100, Martin Blumenstingl wrote: > >> usb_phy_roothub_exit() should return the error code from the phy_exit() > >> call if