On Thu, Jun 13, 2024 at 1:04 AM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > On Wed, Jun 12, 2024 at 11:39:22PM +0800, joswang wrote: > > From: Jos Wang <joswang@xxxxxxxxxx> > > > > This is a workaround for STAR 4846132, which only affects > > DWC_usb31 version2.00a operating in host mode. > > > > There is a problem in DWC_usb31 version 2.00a operating > > in host mode that would cause a CSR read timeout When CSR > > read coincides with RAM Clock Gating Entry. By disable > > Clock Gating, sacrificing power consumption for normal > > operation. > > > > Cc: stable@xxxxxxxxxxxxxxx > > Signed-off-by: Jos Wang <joswang@xxxxxxxxxx> > > --- > > v1 -> v2: > > - add "dt-bindings: usb: dwc3: Add snps,p2p3tranok quirk" patch, > > this patch does not make any changes > > v2 -> v3: > > - code refactor > > - modify comment, add STAR number, workaround applied in host mode > > - modify commit message, add STAR number, workaround applied in host mode > > - modify Author Jos Wang > > v3 -> v4: > > - modify commit message, add Cc: stable@xxxxxxxxxxxxxxx > > This thread is crazy, look at: > https://lore.kernel.org/all/20240612153922.2531-1-joswang1221@xxxxxxxxx/ > for how it looks. How do I pick out the proper patches to review/apply > there at all? What would you do if you were in my position except just > delete the whole thing? > > Just properly submit new versions of patches (hint, without the ','), as > the documentation file says to, as new threads each time, with all > commits, and all should be fine. > > We even have tools that can do this for you semi-automatically, why not > use them? > > thanks, > > greg k-h We apologize for any inconvenience this may cause. The following incorrect operation caused the problem you mentioned: git send-email --in-reply-to command sends the new version patch git format-patch --subject-prefix='PATCH v3 Should I resend the v5 patch now?
