From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: usb tree branch usb-linus merge plan ?
Date: Tue, 28 Mar 2023 19:32:25 +0200 [thread overview]
Message-ID: <ZCMkqSD8-DtaY6Oc@kroah.com> (raw)
In-Reply-To: <a61062edbd266f6c8a260fd30886a97242133ea0.camel@infinera.com>
On Tue, Mar 28, 2023 at 05:25:20PM +0000, Joakim Tjernlund wrote:
> On Wed, 2023-03-22 at 14:55 +0100, Joakim Tjernlund wrote:
> > On Wed, 2023-03-22 at 12:42 +0100, Greg KH wrote:
> > > On Wed, Mar 22, 2023 at 10:22:28AM +0000, Joakim Tjernlund wrote:
> > > > In https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Fgregkh%2Fusb.git%2Flog%2F%3Fh%3Dusb-linus&data=05%7C01%7CJoakim.Tjernlund%40infinera.com%7Cd0efe8021d0b43a707b908db2aca907b%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C638150821713395063%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=z3vZ9PJ05Ty5JxE76hbPPphJer9AtAWR9nHiAZujoDc%3D&reserved=0 there UCSI fixes that
> > > > prevent OOPS in stable Linux.
> > >
> > > What specific commit are you concerned about?
> >
> > usb: ucsi_acpi: Increase the command completion timeout
> > usb: ucsi: Fix ucsi->connector race
> > usb: ucsi: Fix NULL pointer deref in ucsi_connector_change()
> >
> > They have been there for 13 days and I started to wonder if they were delayed or marked for a much later release.
> >
> > >
> > > > I don't see any of them in Linus tree and wonder if these are planned for later?
> > >
> > > Hopefully they will get sent to Linus later this week. Is there a
> > > specific rush that you need this now?
> >
> > Later this week is fine.
> >
> > Thanks
> > Jocke
> >
>
> I noticed above UCSI patches in the stable queue except this one : "usb: ucsi: Fix ucsi->connector race",
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0482c34ec6f8557e06cd0f8e2d0e20e8ede6a22c
> Marked for stable, perhaps forgotten ?
Nope, does not apply:
https://lore.kernel.org/all/16800048817970@kroah.com/
(also for other branches.)
If you can provide a working backport, I will gladly apply it.
thanks,
greg k-h
next prev parent reply other threads:[~2023-03-28 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 10:22 usb tree branch usb-linus merge plan ? Joakim Tjernlund
2023-03-22 11:42 ` Greg KH
2023-03-22 13:55 ` Joakim Tjernlund
2023-03-28 17:25 ` Joakim Tjernlund
2023-03-28 17:32 ` gregkh [this message]
2023-03-29 8:05 ` Joakim Tjernlund
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=ZCMkqSD8-DtaY6Oc@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Joakim.Tjernlund@infinera.com \
--cc=linux-usb@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