public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Tomasz Rostanski <tomasz.rostanski@thalesgroup.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Stable <stable@vger.kernel.org>,
	Linux USB <linux-usb@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Alexander Stein <alexander.stein@ew.tq-group.com>,
	Sasha Levin <sashal@kernel.org>
Subject: Re: Fwd: dwc3: regression in USB DWC3 driver in kernel 5.15 branch
Date: Fri, 24 Nov 2023 16:18:59 +0000	[thread overview]
Message-ID: <2023112424-escalate-saga-2b01@gregkh> (raw)
In-Reply-To: <f7d315b1-f43d-4573-81f0-a4014f3ac0bb@leemhuis.info>

On Tue, Nov 21, 2023 at 04:25:30PM +0100, Thorsten Leemhuis wrote:
> Hi. Top-posting for once, to make this easily accessible to everyone.
> 
> To Greg and everyone that might care: apparently Tomasz lost interest in
> fixing this 5.15.y regression. Kinda sad, as the patches are mostly
> there, but lack a S-o-b tag -- which means we are stuck here, unless
> somebody else attempts a backport.
> 
> https://lore.kernel.org/all/20230904071432.32309-1-tomasz.rostanski@thalesgroup.com/
> 
> I'll thus stop tracking this regression.

Thanks, I'll wait for a working backport for those using the 5.15.y tree
and this driver as it's not anything that I am capable of doing at this
point in time.

greg k-h

      reply	other threads:[~2023-11-24 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-15 11:03 Fwd: dwc3: regression in USB DWC3 driver in kernel 5.15 branch Bagas Sanjaya
2023-07-16 14:58 ` Greg Kroah-Hartman
2023-11-01 18:59 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-21 15:25   ` Thorsten Leemhuis
2023-11-24 16:18     ` Greg Kroah-Hartman [this message]

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=2023112424-escalate-saga-2b01@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=bagasdotme@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tomasz.rostanski@thalesgroup.com \
    /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