From: Greg KH <gregkh@linuxfoundation.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: rgerganov@vmware.com, felipe.balbi@linux.intel.com,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] USB: gadget: f_hid: fix deadlock in f_hidg_write()" failed to apply to 4.9-stable tree
Date: Sat, 30 Mar 2019 21:23:07 +0100 [thread overview]
Message-ID: <20190330202307.GA27435@kroah.com> (raw)
In-Reply-To: <1553976383.2893.15.camel@HansenPartnership.com>
On Sat, Mar 30, 2019 at 01:06:23PM -0700, James Bottomley wrote:
> On Sat, 2019-03-30 at 20:57 +0100, gregkh@linuxfoundation.org wrote:
> > The patch below does not apply to the 4.9-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>.
>
> [...]
>
> > Cc: stable@vger.kernel.org # 4.11+
> > Fixes: 749494b6bdbb ("usb: gadget: f_hid: fix: Move IN request
> > allocation to set_alt()")
>
> The cc: stable specifies 4.11+ because the commit it fixes went in in
> the 4.11 merge window. Is there something incorrect with the tagging
> that makes you think it should apply to 4.9?
Commit 749494b6bdbb originally showed up in 4.11, but it was then
backported to 4.10.2 and 4.9.90. That is why I tried to apply it to
4.9.y and when it did not work, sent out the rejection notice.
thanks,
greg k-h
next prev parent reply other threads:[~2019-03-30 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 19:57 FAILED: patch "[PATCH] USB: gadget: f_hid: fix deadlock in f_hidg_write()" failed to apply to 4.9-stable tree gregkh
2019-03-30 20:06 ` James Bottomley
2019-03-30 20:23 ` Greg KH [this message]
2019-03-30 20:55 ` James Bottomley
2019-03-30 20:23 ` Sasha Levin
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=20190330202307.GA27435@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=felipe.balbi@linux.intel.com \
--cc=rgerganov@vmware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.