public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: joswang <joswang1221@gmail.com>, Greg KH <gregkh@linuxfoundation.org>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Jos Wang <joswang@lenovo.com>
Subject: Re: [PATCH v7] usb: dwc3: core: Workaround for CSR read timeout
Date: Wed, 26 Jun 2024 01:37:14 +0000	[thread overview]
Message-ID: <20240626013710.dxqa6r4mjuc6on4w@synopsys.com> (raw)
In-Reply-To: <CAMtoTm2UE31gcM7dGxvz_CbFoKotOJ1p7PeQwgBuTDE9nq7CJw@mail.gmail.com>

On Tue, Jun 25, 2024, joswang wrote:
> On Sat, Jun 22, 2024 at 7:09 AM Thinh Nguyen <Thinh.Nguyen@synopsys.com> wrote:
> >
> > Ok. I may have misunderstood what can go into rc2 and beyond then. If we
> > don't have to wait for the next rc1 for it to be picked up for stable,
> > then can we add it to "usb-linus" branch?
> >
> > There won't be a Fixes tag, but we can backport it up to 5.10.x:
> >
> > Cc: <stable@vger.kernel.org> # 5.10.x: 1e43c86d: usb: dwc3: core: Add DWC31 version 2.00a controller
> > Cc: <stable@vger.kernel.org> # 5.10.x
> >
> > This can go after the versioning scheme in dwc3 in the 5.10.x lts. I did
> > not check what other dependencies are needed in addition to the change
> > above.
> >
> > Thanks,
> > Thinh
> 
> Is there anything else I need to modify for this patch?
> 

Hi Greg,

Will a simple tag "Cc: <stable@vger.kernel.org>" sufficient? Or would
you prefer using the tags above?

For either case:

Acked-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>

Thanks,
Thinh

  reply	other threads:[~2024-06-26  1:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 11:45 [PATCH v7] usb: dwc3: core: Workaround for CSR read timeout joswang
2024-06-20 17:16 ` Greg KH
2024-06-21  1:40   ` joswang
2024-06-21  5:19     ` Greg KH
2024-06-21  5:42       ` Thinh Nguyen
2024-06-21  5:49         ` Greg KH
2024-06-21  6:20           ` Thinh Nguyen
2024-06-21  7:09             ` Greg KH
2024-06-21 23:09               ` Thinh Nguyen
2024-06-25 12:23                 ` joswang
2024-06-26  1:37                   ` Thinh Nguyen [this message]
2024-06-27 14:26                     ` Greg KH

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=20240626013710.dxqa6r4mjuc6on4w@synopsys.com \
    --to=thinh.nguyen@synopsys.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joswang1221@gmail.com \
    --cc=joswang@lenovo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox