public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Forest <forestix@nom.one>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>,
	linux-usb@vger.kernel.org, regressions@lists.linux.dev,
	stable@vger.kernel.org
Subject: Re: [REGRESSION] usb: xhci port capability storage change broke fastboot android bootloader utility
Date: Wed, 15 Jan 2025 08:33:13 +0100	[thread overview]
Message-ID: <2025011547-ditch-dust-bda4@gregkh> (raw)
In-Reply-To: <h74eojd2r7t9f9jh3ebt07dlrhh6etqv4q@sonic.net>

On Tue, Jan 14, 2025 at 05:38:54PM -0800, Forest wrote:
> On Mon, 13 Jan 2025 17:05:09 +0200, Mathias Nyman wrote:
> 
> >I'd recommend a patch that permanently adds USB_QUIRK_NO_LPM for this device.
> >Let me know if you want to submit it yourself, otherwise I can do it.
> 
> Thank you.
> 
> I have prepared a patch against 6.13-rc7. This regression also affects the
> stable branch, but I don't know the patch policy for stable. To which lists
> should I send the patch?

Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

(hint, get it into Linus's tree first before worrying about stable
backports.)

thanks,

greg k-h

  reply	other threads:[~2025-01-15  7:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-27 21:59 [REGRESSION] usb: xhci port capability storage change broke fastboot android bootloader utility Forest
2025-01-02 14:13 ` Mathias Nyman
2025-01-05 23:42   ` Forest
2025-01-07 12:29     ` Mathias Nyman
2025-01-11  0:00       ` Forest
2025-01-13 15:05         ` Mathias Nyman
2025-01-15  1:38           ` Forest
2025-01-15  7:33             ` Greg KH [this message]
2025-01-24 19:44           ` Forest
2025-01-29 11:01             ` Mathias Nyman
2025-02-13 20:24               ` Salvatore Bonaccorso
2025-02-14 12:29                 ` Mathias Nyman
2025-02-14 15:55                   ` Salvatore Bonaccorso

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=2025011547-ditch-dust-bda4@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=forestix@nom.one \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=regressions@lists.linux.dev \
    --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