From: Greg KH <greg@kroah.com>
To: bugzilla-daemon@kernel.org
Cc: linux-usb@vger.kernel.org
Subject: Re: [Bug 217670] New: Regression in USB DWC3 driver in kernel 5.15 branch
Date: Sun, 16 Jul 2023 16:59:37 +0200 [thread overview]
Message-ID: <2023071621-relation-unlocking-93ed@gregkh> (raw)
In-Reply-To: <bug-217670-208809@https.bugzilla.kernel.org/>
On Fri, Jul 14, 2023 at 01:18:29PM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=217670
>
> Bug ID: 217670
> Summary: Regression in USB DWC3 driver in kernel 5.15 branch
> Product: Drivers
> Version: 2.5
> Hardware: ARM
> OS: Linux
> Status: NEW
> Severity: normal
> Priority: P3
> Component: USB
> Assignee: drivers_usb@kernel-bugs.kernel.org
> Reporter: tomasz.rostanski@thalesgroup.com
> Regression: No
>
> The backport commit to 5.15 branch:
> 9d4f84a15f9c9727bc07f59d9dafc89e65aadb34 "arm64: dts: imx8mp: Add
> snps,gfladj-refclk-lpm-sel quirk to USB nodes" (from upstream commit
> 5c3d5ecf48ab06c709c012bf1e8f0c91e1fcd7ad)
> switched from "snps,dis-u2-freeclk-exists-quirk" to
> "snps,gfladj-refclk-lpm-sel-quirk".
>
> The problem is that the gfladj-refclk-lpm-sel-quirk quirk is not implemented /
> backported to 5.15 branch.
>
> This commit should be either reverted, or the commit introducing
> gfladj-refclk-lpm-sel-quirk needs to be merged to 5.15 kernel branch.
What commit exactly needs to be backported?
thanks,
greg k-h
next prev parent reply other threads:[~2023-07-16 15:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 13:18 [Bug 217670] New: Regression in USB DWC3 driver in kernel 5.15 branch bugzilla-daemon
2023-07-14 13:28 ` [Bug 217670] dwc3: regression " bugzilla-daemon
2023-07-14 13:29 ` bugzilla-daemon
2023-07-14 13:30 ` bugzilla-daemon
2023-07-16 14:59 ` Greg KH [this message]
2023-07-16 15:00 ` bugzilla-daemon
2023-07-17 5:20 ` bugzilla-daemon
2023-07-17 6:36 ` bugzilla-daemon
2023-07-17 14:30 ` Greg KH
2023-07-17 14:30 ` bugzilla-daemon
2023-07-18 5:25 ` bugzilla-daemon
2023-08-31 9:12 ` bugzilla-daemon
2023-08-31 9:19 ` bugzilla-daemon
2023-08-31 9:31 ` bugzilla-daemon
2023-08-31 10:56 ` Greg KH
2023-08-31 10:56 ` bugzilla-daemon
2023-09-01 9:22 ` bugzilla-daemon
2023-09-01 12:53 ` bugzilla-daemon
2023-09-01 12:53 ` bugzilla-daemon
2023-09-01 12:53 ` bugzilla-daemon
2023-09-01 12:54 ` bugzilla-daemon
2023-09-01 12:54 ` bugzilla-daemon
2023-09-01 12:54 ` bugzilla-daemon
2023-09-01 12:55 ` bugzilla-daemon
2023-09-01 12:55 ` bugzilla-daemon
2023-09-01 12:56 ` bugzilla-daemon
2023-09-01 12:56 ` bugzilla-daemon
2023-09-01 12:57 ` bugzilla-daemon
2023-09-01 13:14 ` Greg KH
2023-09-01 13:13 ` bugzilla-daemon
2023-09-01 13:14 ` bugzilla-daemon
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=2023071621-relation-unlocking-93ed@gregkh \
--to=greg@kroah.com \
--cc=bugzilla-daemon@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.