Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Michał Pecio" <michal.pecio@gmail.com>
Cc: mathias.nyman@linux.intel.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] xhci: handle isoc Babble and Buffer Overrun events properly" failed to apply to 5.10-stable tree
Date: Tue, 13 Feb 2024 15:18:43 +0100	[thread overview]
Message-ID: <2024021322-snitch-pauper-fd9c@gregkh> (raw)
In-Reply-To: <2024021351-overstay-crisply-f6af@gregkh>

On Tue, Feb 13, 2024 at 03:17:36PM +0100, Greg KH wrote:
> On Tue, Feb 13, 2024 at 02:39:21PM +0100, Michał Pecio wrote:
> > Hi,
> > 
> > > The patch below does not apply to the 5.10-stable tree.
> > > [...]
> > > From 7c4650ded49e5b88929ecbbb631efb8b0838e811 Mon Sep 17 00:00:00 2001
> > > From: Michal Pecio <michal.pecio@gmail.com>
> > > Date: Thu, 25 Jan 2024 17:27:37 +0200
> > > Subject: [PATCH] xhci: handle isoc Babble and Buffer Overrun events
> > 
> > This patch depends on its parent 5372c65e1311 ("xhci: process isoc TD
> > properly when there was a transaction error mid TD.").
> > 
> > The parent commit appears to be missing from your 5.10 and earlier
> > queues for some reason, hence the breakage.
> 
> That parent commit would not apply to those older kernels (and I had no
> hint that it should go there.)  I've backported it to 5.10.y ok, but 5.4
> and 4.19 were harder.  So if you want both of these in those older
> kernels, please provide working backports and I'll be glad to queue them
> up.

Nope, my 5.10.y backport failed too, so will need working versions for
that tree as well.

thanks,

greg k-h

      reply	other threads:[~2024-02-13 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 13:22 FAILED: patch "[PATCH] xhci: handle isoc Babble and Buffer Overrun events properly" failed to apply to 5.10-stable tree gregkh
2024-02-13 13:39 ` Michał Pecio
2024-02-13 14:17   ` Greg KH
2024-02-13 14:18     ` Greg KH [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=2024021322-snitch-pauper-fd9c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=michal.pecio@gmail.com \
    --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