From: Greg KH <gregkh@linuxfoundation.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: stable@vger.kernel.org, samsun1006219@gmail.com, xrivendell7@gmail.com
Subject: Re: FAILED: patch "[PATCH] USB: core: Fix deadlock in usb_deauthorize_interface()" failed to apply to 4.19-stable tree
Date: Mon, 1 Apr 2024 16:52:31 +0200 [thread overview]
Message-ID: <2024040119-uncommon-premises-62a4@gregkh> (raw)
In-Reply-To: <40fa743b-97cc-4172-96eb-1d55a54784aa@rowland.harvard.edu>
On Mon, Apr 01, 2024 at 09:59:14AM -0400, Alan Stern wrote:
> On Mon, Apr 01, 2024 at 11:42:57AM +0200, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 4.19-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> >
> > To reproduce the conflict and resubmit, you may use the following commands:
> >
> > git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-4.19.y
> > git checkout FETCH_HEAD
> > git cherry-pick -x 80ba43e9f799cbdd83842fc27db667289b3150f5
> > # <resolve conflicts, build, test, etc.>
> > git commit -s
> > git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2024040157-entrench-clicker-d3df@gregkh' --subject-prefix 'PATCH 4.19.y' HEAD^..
> >
> > Possible dependencies:
> >
> > 80ba43e9f799 ("USB: core: Fix deadlock in usb_deauthorize_interface()")
> >
> > thanks,
> >
> > greg k-h
>
> Here is the back-ported version of the patch. It was necessary to change
> kstrtobool to strtobool.
>
> This should apply to the -stable kernels from 4.19 up to 6.1.
Thanks, now queued up!
greg k-h
prev parent reply other threads:[~2024-04-01 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 9:42 FAILED: patch "[PATCH] USB: core: Fix deadlock in usb_deauthorize_interface()" failed to apply to 4.19-stable tree gregkh
2024-04-01 13:59 ` Alan Stern
2024-04-01 14:52 ` 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=2024040119-uncommon-premises-62a4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=samsun1006219@gmail.com \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=xrivendell7@gmail.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