mbox series

[v1,0/2] usb: dwc3: revert OTG changes for Intel Merrifield

Message ID 20220923163051.36288-1-andriy.shevchenko@linux.intel.com (mailing list archive)
Headers show
Series usb: dwc3: revert OTG changes for Intel Merrifield | expand

Message

Andy Shevchenko Sept. 23, 2022, 4:30 p.m. UTC
It's late in the cycle, that's why I send these reverts, so we will have a
full new cycle for testing a better solution if any.

So this is just a proactive move if we have no solution in the nearest days.

Andy Shevchenko (2):
  Revert "USB: fixup for merge issue with "usb: dwc3: Don't switch OTG
    -> peripheral if extcon is present""
  Revert "usb: dwc3: Don't switch OTG -> peripheral if extcon is
    present"

 drivers/usb/dwc3/core.c | 50 +----------------------------------------
 drivers/usb/dwc3/drd.c  | 50 +++++++++++++++++++++++++++++++++++++++++
 2 files changed, 51 insertions(+), 49 deletions(-)

Comments

Ferry Toth Sept. 23, 2022, 8:34 p.m. UTC | #1
Hi

Op 23-09-2022 om 18:30 schreef Andy Shevchenko:
> It's late in the cycle, that's why I send these reverts, so we will have a
> full new cycle for testing a better solution if any.
>
> So this is just a proactive move if we have no solution in the nearest days.
>
> Andy Shevchenko (2):
>    Revert "USB: fixup for merge issue with "usb: dwc3: Don't switch OTG
>      -> peripheral if extcon is present""
>    Revert "usb: dwc3: Don't switch OTG -> peripheral if extcon is
>      present"
>
>   drivers/usb/dwc3/core.c | 50 +----------------------------------------
>   drivers/usb/dwc3/drd.c  | 50 +++++++++++++++++++++++++++++++++++++++++
>   2 files changed, 51 insertions(+), 49 deletions(-)
>
For the series:

Tested-by: Ferry Toth <fntoth@gmail.com> # for Merrifield
Greg Kroah-Hartman Sept. 24, 2022, 10:39 a.m. UTC | #2
On Fri, Sep 23, 2022 at 07:30:49PM +0300, Andy Shevchenko wrote:
> It's late in the cycle, that's why I send these reverts, so we will have a
> full new cycle for testing a better solution if any.

Wait, you need these into what release?  6.1-rc1?

The commits you are referencing are in 5.19, right?  Not 6.0-rc.

> So this is just a proactive move if we have no solution in the nearest days.

How will I know this?

confused,

greg k-h