From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Felipe Balbi <balbi@kernel.org>
Subject: Re: [PATCH v1 0/2] usb: dwc3: revert OTG changes for Intel Merrifield
Date: Sat, 24 Sep 2022 12:39:13 +0200 [thread overview]
Message-ID: <Yy7eUZh6sWbDekEC@kroah.com> (raw)
In-Reply-To: <20220923163051.36288-1-andriy.shevchenko@linux.intel.com>
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
prev parent reply other threads:[~2022-09-24 10:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 16:30 [PATCH v1 0/2] usb: dwc3: revert OTG changes for Intel Merrifield Andy Shevchenko
2022-09-23 16:30 ` [PATCH v1 1/2] Revert "USB: fixup for merge issue with "usb: dwc3: Don't switch OTG -> peripheral if extcon is present"" Andy Shevchenko
2022-09-24 10:39 ` Greg Kroah-Hartman
2022-09-23 16:30 ` [PATCH v1 2/2] Revert "usb: dwc3: Don't switch OTG -> peripheral if extcon is present" Andy Shevchenko
2022-09-24 10:40 ` Greg Kroah-Hartman
2022-09-23 20:34 ` [PATCH v1 0/2] usb: dwc3: revert OTG changes for Intel Merrifield Ferry Toth
2022-09-24 10:39 ` Greg Kroah-Hartman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yy7eUZh6sWbDekEC@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrew.smirnov@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=balbi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.