From: Salvatore Bonaccorso <carnil@debian.org>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: Forest <forestix@nom.one>,
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: Thu, 13 Feb 2025 21:24:22 +0100 [thread overview]
Message-ID: <Z65U9rZrZUjofo02@eldamar.lan> (raw)
In-Reply-To: <ee229b33-2082-4e03-8f2b-df5b4a86a77d@linux.intel.com>
Hi Mathias,
On Wed, Jan 29, 2025 at 01:01:58PM +0200, Mathias Nyman wrote:
> On 24.1.2025 21.44, 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.
> >
> > It looks like I can't contribute a patch after all, due to an issue with my
> > Signed-off-by signature.
> >
> > So, can you take care of the quirk patch for this device?
> >
> > Thank you.
>
> Sure, I'll send it after rc1 is out next week
Not something superurgent, but wanted to ask is that still on your
radaar? I stumpled over it while looking at the current open bugs
reported in Debian, reminding me of https://bugs.debian.org/1091517
Thanks for your work!
Regards,
Salvatore
next prev parent reply other threads:[~2025-02-13 20:24 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
2025-01-24 19:44 ` Forest
2025-01-29 11:01 ` Mathias Nyman
2025-02-13 20:24 ` Salvatore Bonaccorso [this message]
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=Z65U9rZrZUjofo02@eldamar.lan \
--to=carnil@debian.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;
as well as URLs for NNTP newsgroup(s).