All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Moritz Fischer <moritz.fischer.private@gmail.com>,
	Moritz Fischer <mdf@kernel.org>, Vinod Koul <vkoul@kernel.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: REGRESSION: Renesas USB host broken after commit d143825baf15
Date: Wed, 21 Jul 2021 09:54:27 +0200	[thread overview]
Message-ID: <YPfSsx8p32w72OCB@kroah.com> (raw)
In-Reply-To: <s5h1r7snneh.wl-tiwai@suse.de>

On Wed, Jul 21, 2021 at 09:20:38AM +0200, Takashi Iwai wrote:
> On Wed, 21 Jul 2021 01:29:22 +0200,
> Moritz Fischer wrote:
> > 
> > Hi Takashi,
> > 
> > On Wed, Jul 21, 2021 at 01:06:29AM +0200, Takashi Iwai wrote:
> > > Hi,
> > > 
> > > the recent patch landed in 5.13.2 stable tree from the upstream commit
> > > d143825baf15 ("usb: renesas-xhci: Fix handling of unknown ROM state")
> > > seems causing a regression on a few machines, as reported on openSUSE
> > > Bugzilla:
> > >   https://bugzilla.opensuse.org/show_bug.cgi?id=1188485
> > >   https://bugzilla.opensuse.org/show_bug.cgi?id=1188515
> > > 
> > > Reverting it on top of 5.13.3 fixed the problem, so it's likely the
> > > cause.  Could you guys take a look?
> > 
> > I've sent out a revert patch.
> > 
> > https://lore.kernel.org/linux-usb/20210719070519.41114-1-mdf@kernel.org/T/#u
> > 
> > I think the driver has more problems but I'll tackle that in a follow up
> > patch, lets get this unbricked, first.
> 
> OK, thank you for the information!

I've reverted this now, will get it to Linus for 5.14-rc3, sorry about
that.

thanks,

greg k-h

      reply	other threads:[~2021-07-21  7:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 23:06 REGRESSION: Renesas USB host broken after commit d143825baf15 Takashi Iwai
2021-07-20 23:29 ` Moritz Fischer
2021-07-21  7:20   ` Takashi Iwai
2021-07-21  7:54     ` 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=YPfSsx8p32w72OCB@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=moritz.fischer.private@gmail.com \
    --cc=tiwai@suse.de \
    --cc=vkoul@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.